Start free
ActionSquareUpdated June 2026

How do I search Square orders?

Short answer: You can search square orders in Square by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Square Search Square Orders action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Search Square Orders in Square — start free All 8 Square actions
Search Square Orders in Square — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Location IDs
location_ids
arrayRequired–
Limit
limit
stringOptional–
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.

Triggered by

Apps that pair well as the trigger for Search Square Orders.

Any of these apps can fire this action as part of a workflow.

Gmail → Square
1 Gmail triggers
Slack → Square
13 Slack triggers
Google Sheets → Square
2 Google Sheets triggers
HubSpot → Square
18 HubSpot triggers
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. TinyCommand 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.
Action
Create 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.
Action
Square Create Payment
Charges a saved customer card or processes a payment with provided source. For "external order completed → charge via Square" workflows.
Action
List Square Locations
Returns the merchant's locations. Useful for resolving location IDs and for multi-location reporting workflows.
Action
List Square Payments
Paginated payments with filters by date, location, status. For revenue-reporting workflows and for accounting reconciliation.
Action
Refund Square Payment
Refunds full or partial. For "customer requested refund via support" or "fraud detection → auto-refund" workflows.
Search Square Orders in Square — start free