Search Gorgias Customers: Gorgias 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
Email email	string	Required	The email address. Used as the recipient or identifier depending on context.

Sample request

{
  "email": "e.g. user@example.com"
}

Returns

{
  "data": [
    {
      "id": 42,
      "name": "Jane Doe",
      "email": "jane@x.com"
    }
  ]
}

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

FAQ

Questions about Search Gorgias Customers.

What does the Search Gorgias Customers action do in Gorgias?

Lookup by email or external ID. Useful for "incoming chat from email X → find existing customer to attribute the ticket" workflows.

What inputs does Search Gorgias Customers require?

Required: Email. 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 Gorgias 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 Gorgias Customers support batch operations?

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

More actions