Search Square Orders: Square action

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
Location IDs location_ids	array	Required	—
Limit limit	string	Optional	—

Sample request

{
  "location_ids": "{{trigger.location_ids}}",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "orders": [
    {
      "id": "ord_abc",
      "state": "OPEN",
      "total_money": {
        "amount": 1000
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Search Square Orders.

What does the Search Square Orders action do in Square?

Returns paginated orders with filters by date, location, state. For "today's orders" rollups and for sync to accounting systems.

What inputs does Search Square Orders require?

Required: Location IDs. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Search Square Orders support batch operations?

Yes. Run Search Square Orders 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