Skip to content
ActionSquareUpdated May 2026

What Square locations exist?

Short answer: Drop the "SquareList Square Locations" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Sample request
{}
Returns
{
"locations": [
{
"id": "loc_abc",
"name": "Main Store",
"status": "ACTIVE"
}
]
}

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

Triggered by

Apps that pair well as the trigger for List Square Locations.

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

FAQ

Questions about List Square Locations.

What does the List Square Locations action do in Square?
Returns the merchant's locations. Useful for resolving location IDs and for multi-location reporting workflows.
What inputs does List Square Locations require?
List Square Locations 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 Locations support batch operations?
Yes. Run List Square Locations 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.

Send list square locations from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.