Square Automation via Rube MCP
Automate Square payment processing, order management, and invoicing through Composio's Square toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Square connection via
RUBE_MANAGE_CONNECTIONS with toolkit square
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit square
- If connection is not ACTIVE, follow the returned auth link to complete Square OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. List and Monitor Payments
When to use: User wants to view payment history or check payment status
Tool sequence:
SQUARE_LIST_PAYMENTS - Retrieve payments with optional filters [Required]
SQUARE_CANCEL_PAYMENT - Cancel a pending payment if needed [Optional]
Key parameters:
begin_time / end_time: RFC 3339 timestamps for date range filtering
sort_order: 'ASC' or 'DESC' for chronological ordering
cursor: Pagination cursor from previous response
location_id: Filter payments by specific location
Pitfalls:
- Timestamps must be RFC 3339 format (e.g., '2024-01-01T00:00:00Z')
- Pagination required for large result sets; follow
cursor until absent
- Only pending payments can be cancelled; completed payments require refunds
SQUARE_CANCEL_PAYMENT requires exact payment_id from list results
2. Search and Manage Orders
When to use: User wants to find orders by criteria or update order details
Tool sequence:
SQUARE_LIST_LOCATIONS - Get location IDs for filtering [Prerequisite]
SQUARE_SEARCH_ORDERS - Search orders with filters [Required]
SQUARE_RETRIEVE_ORDER - Get full details of a specific order [Optional]
SQUARE_UPDATE_ORDER - Modify order state or details [Optional]
Key parameters:
location_ids: Array of location IDs to search within (required for search)
query: Search filter object with date ranges, states, fulfillment types
order_id: Specific order ID for retrieve/update operations
cursor: Pagination cursor for search results
Pitfalls:
location_ids is required for SEARCH_ORDERS; get IDs from LIST_LOCATIONS first
- Order states include: OPEN, COMPLETED, CANCELED, DRAFT
- UPDATE_ORDER requires the current
version field to prevent conflicts
- Search results are paginated; follow
cursor until absent
3. Manage Locations
When to use: User wants to view business locations or get location details
Tool sequence:
SQUARE_LIST_LOCATIONS - List all business locations [Required]
Key parameters:
- No required parameters; returns all accessible locations
- Response includes
id, name, address, status, timezone
Pitfalls:
- Location IDs are required for most other Square operations (orders, payments)
- Always cache location IDs after first retrieval to avoid redundant calls
- Inactive locations may still appear in results; check
status field
4. Invoice Management
When to use: User wants to list, view, or cancel invoices
Tool sequence:
SQUARE_LIST_LOCATIONS - Get location ID for filtering [Prerequisite]
SQUARE_LIST_INVOICES - List invoices for a location [Required]
SQUARE_GET_INVOICE - Get detailed invoice information [Optional]
SQUARE_CANCEL_INVOICE - Cancel a scheduled or unpaid invoice [Optional]
Key parameters:
location_id: Required for listing invoices
invoice_id: Required for get/cancel operations
cursor: Pagination cursor for list results
limit: Number of results per page
Pitfalls:
location_id is required for LIST_INVOICES; resolve via LIST_LOCATIONS first
- Only SCHEDULED, UNPAID, or PARTIALLY_PAID invoices can be cancelled
- CANCEL_INVOICE requires the invoice
version to prevent race conditions
- Cancelled invoices cannot be uncancelled
Common Patterns
ID Resolution
Location name -> Location ID:
1. Call SQUARE_LIST_LOCATIONS
2. Find location by name in response
3. Extract id field (e.g., 'L1234ABCD')
Order lookup:
1. Call SQUARE_SEARCH_ORDERS with location_ids and query filters
2. Extract order_id from results
3. Use order_id for RETRIEVE_ORDER or UPDATE_ORDER
Pagination
- Check response for
cursor field
- Pass cursor value in next request's
cursor parameter
- Continue until
cursor is absent or empty
- Use
limit to control page size
Date Range Filtering
- Use RFC 3339 format:
2024-01-01T00:00:00Z
- For payments:
begin_time and end_time parameters
- For orders: Use query filter with date_time_filter
- All timestamps are in UTC
Known Pitfalls
ID Formats:
- Location IDs are alphanumeric strings (e.g., 'L1234ABCD')
- Payment IDs and Order IDs are longer alphanumeric strings
- Always resolve location names to IDs before other operations
Versioning:
- UPDATE_ORDER and CANCEL_INVOICE require current
version field
- Fetch the resource first to get its current version
- Version mismatch returns a 409 Conflict error
Rate Limits:
- Square API has per-endpoint rate limits
- Implement backoff for bulk operations
- Pagination should include brief delays for large datasets
Response Parsing:
- Responses may nest data under
data key
- Money amounts are in smallest currency unit (cents for USD)
- Parse defensively with fallbacks for optional fields
Quick Reference
| Task |
Tool Slug |
Key Params |
| List payments |
SQUARE_LIST_PAYMENTS |
begin_time, end_time, location_id, cursor |
| Cancel payment |
SQUARE_CANCEL_PAYMENT |
payment_id |
| Search orders |
SQUARE_SEARCH_ORDERS |
location_ids, query, cursor |
| Get order |
SQUARE_RETRIEVE_ORDER |
order_id |
| Update order |
SQUARE_UPDATE_ORDER |
order_id, version |
| List locations |
SQUARE_LIST_LOCATIONS |
(none) |
| List invoices |
SQUARE_LIST_INVOICES |
location_id, cursor |
| Get invoice |
SQUARE_GET_INVOICE |
invoice_id |
| Cancel invoice |
SQUARE_CANCEL_INVOICE |
invoice_id, version |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
1---2name: square-automation3description: "Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas."4requires:5 mcp: [rube]6risk: unknown7source: community8metadata:9 source: https://skillmd.com/skills/mayurrathi/square-automation10---1112# Square Automation via Rube MCP1314Automate Square payment processing, order management, and invoicing through Composio's Square toolkit via Rube MCP.1516## Prerequisites1718- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)19- Active Square connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `square`20- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2122## Setup2324**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.2526271. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds282. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `square`293. If connection is not ACTIVE, follow the returned auth link to complete Square OAuth304. Confirm connection status shows ACTIVE before running any workflows3132## Core Workflows3334### 1. List and Monitor Payments3536**When to use**: User wants to view payment history or check payment status3738**Tool sequence**:391. `SQUARE_LIST_PAYMENTS` - Retrieve payments with optional filters [Required]402. `SQUARE_CANCEL_PAYMENT` - Cancel a pending payment if needed [Optional]4142**Key parameters**:43- `begin_time` / `end_time`: RFC 3339 timestamps for date range filtering44- `sort_order`: 'ASC' or 'DESC' for chronological ordering45- `cursor`: Pagination cursor from previous response46- `location_id`: Filter payments by specific location4748**Pitfalls**:49- Timestamps must be RFC 3339 format (e.g., '2024-01-01T00:00:00Z')50- Pagination required for large result sets; follow `cursor` until absent51- Only pending payments can be cancelled; completed payments require refunds52- `SQUARE_CANCEL_PAYMENT` requires exact `payment_id` from list results5354### 2. Search and Manage Orders5556**When to use**: User wants to find orders by criteria or update order details5758**Tool sequence**:591. `SQUARE_LIST_LOCATIONS` - Get location IDs for filtering [Prerequisite]602. `SQUARE_SEARCH_ORDERS` - Search orders with filters [Required]613. `SQUARE_RETRIEVE_ORDER` - Get full details of a specific order [Optional]624. `SQUARE_UPDATE_ORDER` - Modify order state or details [Optional]6364**Key parameters**:65- `location_ids`: Array of location IDs to search within (required for search)66- `query`: Search filter object with date ranges, states, fulfillment types67- `order_id`: Specific order ID for retrieve/update operations68- `cursor`: Pagination cursor for search results6970**Pitfalls**:71- `location_ids` is required for SEARCH_ORDERS; get IDs from LIST_LOCATIONS first72- Order states include: OPEN, COMPLETED, CANCELED, DRAFT73- UPDATE_ORDER requires the current `version` field to prevent conflicts74- Search results are paginated; follow `cursor` until absent7576### 3. Manage Locations7778**When to use**: User wants to view business locations or get location details7980**Tool sequence**:811. `SQUARE_LIST_LOCATIONS` - List all business locations [Required]8283**Key parameters**:84- No required parameters; returns all accessible locations85- Response includes `id`, `name`, `address`, `status`, `timezone`8687**Pitfalls**:88- Location IDs are required for most other Square operations (orders, payments)89- Always cache location IDs after first retrieval to avoid redundant calls90- Inactive locations may still appear in results; check `status` field9192### 4. Invoice Management9394**When to use**: User wants to list, view, or cancel invoices9596**Tool sequence**:971. `SQUARE_LIST_LOCATIONS` - Get location ID for filtering [Prerequisite]982. `SQUARE_LIST_INVOICES` - List invoices for a location [Required]993. `SQUARE_GET_INVOICE` - Get detailed invoice information [Optional]1004. `SQUARE_CANCEL_INVOICE` - Cancel a scheduled or unpaid invoice [Optional]101102**Key parameters**:103- `location_id`: Required for listing invoices104- `invoice_id`: Required for get/cancel operations105- `cursor`: Pagination cursor for list results106- `limit`: Number of results per page107108**Pitfalls**:109- `location_id` is required for LIST_INVOICES; resolve via LIST_LOCATIONS first110- Only SCHEDULED, UNPAID, or PARTIALLY_PAID invoices can be cancelled111- CANCEL_INVOICE requires the invoice `version` to prevent race conditions112- Cancelled invoices cannot be uncancelled113114## Common Patterns115116### ID Resolution117118**Location name -> Location ID**:119```1201. Call SQUARE_LIST_LOCATIONS1212. Find location by name in response1223. Extract id field (e.g., 'L1234ABCD')123```124125**Order lookup**:126```1271. Call SQUARE_SEARCH_ORDERS with location_ids and query filters1282. Extract order_id from results1293. Use order_id for RETRIEVE_ORDER or UPDATE_ORDER130```131132### Pagination133134- Check response for `cursor` field135- Pass cursor value in next request's `cursor` parameter136- Continue until `cursor` is absent or empty137- Use `limit` to control page size138139### Date Range Filtering140141- Use RFC 3339 format: `2024-01-01T00:00:00Z`142- For payments: `begin_time` and `end_time` parameters143- For orders: Use query filter with date_time_filter144- All timestamps are in UTC145146## Known Pitfalls147148**ID Formats**:149- Location IDs are alphanumeric strings (e.g., 'L1234ABCD')150- Payment IDs and Order IDs are longer alphanumeric strings151- Always resolve location names to IDs before other operations152153**Versioning**:154- UPDATE_ORDER and CANCEL_INVOICE require current `version` field155- Fetch the resource first to get its current version156- Version mismatch returns a 409 Conflict error157158**Rate Limits**:159- Square API has per-endpoint rate limits160- Implement backoff for bulk operations161- Pagination should include brief delays for large datasets162163**Response Parsing**:164- Responses may nest data under `data` key165- Money amounts are in smallest currency unit (cents for USD)166- Parse defensively with fallbacks for optional fields167168## Quick Reference169170| Task | Tool Slug | Key Params |171|------|-----------|------------|172| List payments | SQUARE_LIST_PAYMENTS | begin_time, end_time, location_id, cursor |173| Cancel payment | SQUARE_CANCEL_PAYMENT | payment_id |174| Search orders | SQUARE_SEARCH_ORDERS | location_ids, query, cursor |175| Get order | SQUARE_RETRIEVE_ORDER | order_id |176| Update order | SQUARE_UPDATE_ORDER | order_id, version |177| List locations | SQUARE_LIST_LOCATIONS | (none) |178| List invoices | SQUARE_LIST_INVOICES | location_id, cursor |179| Get invoice | SQUARE_GET_INVOICE | invoice_id |180| Cancel invoice | SQUARE_CANCEL_INVOICE | invoice_id, version |181182## When to Use183This skill is applicable to execute the workflow or actions described in the overview.