How to search square customers in Square

Search Square Customers 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.

Field	Type	Required	Description
Email (exact) email	string	Optional	The email address. Used as the recipient or identifier depending on context.
Phone (exact) phone	string	Optional	Phone number in E.164 format (with country code, no spaces).
Limit limit	string	Optional	–

Sample request

{
  "email": "e.g. user@example.com",
  "phone": "e.g. +14155551234",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "customers": [
    {
      "id": "ABC",
      "given_name": "Jane",
      "email_address": "jane@acme.com"
    }
  ]
}

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

FAQ

Questions about Search Square Customers.

What does the Search Square Customers action do in Square?

Lookup by email, phone, name. For "find existing customer record by phone" POS workflows.

What inputs does Search Square Customers require?

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

Yes. Run Search Square Customers inside a Loop node to process arrays. TinyCommand handles Square's rate limits automatically so you don't have to throttle manually.

More actions