- Integrations
- /
- Square
- /
- Actions
- /
- List Square Payments
ActionSquareUpdated May 2026
How do I list Square payments?
Short answer: Drop the "Square → List Square Payments" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Begin Time begin_time | string | Optional | 2026-05-01T00:00:00Z |
End Time end_time | string | Optional | — |
Limit limit | string | Optional | — |
Sample request
{"begin_time": "2026-05-01T00:00:00Z","end_time": "{{trigger.end_time}}","limit": "{{trigger.limit}}"}
Returns
{"payments": [{"id": "pay_abc","status": "COMPLETED","amount_money": {"amount": 1000}}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Square Payments.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Square Payments.
What does the List Square Payments action do in Square?
Paginated payments with filters by date, location, status. For revenue-reporting workflows and for accounting reconciliation.
What inputs does List Square Payments require?
List Square Payments has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Square returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does List Square Payments support batch operations?
Yes. Run List Square Payments inside a Loop node to process arrays. Tiny Command handles Square's rate limits automatically so you don't have to throttle manually.
More actions
Other Square actions.
Action
Create Square Customer
Creates a customer with email, name, address. For "POS customer → push to Square Customers for repeat-business loyalty tracking" workflows.
ActionCreate Square Invoice
Creates an invoice with line items, customer, due date. For service-business workflows where Square is the payment processor but the invoice is generated externally.
ActionSquare Create Payment
Charges a saved customer card or processes a payment with provided source. For "external order completed → charge via Square" workflows.
ActionList Square Locations
Returns the merchant's locations. Useful for resolving location IDs and for multi-location reporting workflows.
ActionRefund Square Payment
Refunds full or partial. For "customer requested refund via support" or "fraud detection → auto-refund" workflows.
ActionSearch Square Customers
Lookup by email, phone, name. For "find existing customer record by phone" POS workflows.
Send list square payments from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.