How to list gorgias tickets in Gorgias

List Gorgias Tickets in Gorgias — 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
Limit limit	string	Optional	–
Status filter status	string	Optional	open or closed
Channel filter channel	string	Optional	–

Sample request

{
  "limit": "{{trigger.limit}}",
  "status": "open or closed",
  "channel": "{{trigger.channel}}"
}

Returns

{
  "data": [
    {
      "id": 1234,
      "status": "open",
      "subject": "Help"
    }
  ],
  "meta": {
    "total_count": 1
  }
}

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

FAQ

Questions about List Gorgias Tickets.

What does the List Gorgias Tickets action do in Gorgias?

Paginated tickets with filters by status, channel, assignee, tags, time range. For "open tickets matching this pattern" routing workflows or daily-summary digests.

What inputs does List Gorgias Tickets require?

List Gorgias Tickets 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 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 List Gorgias Tickets support batch operations?

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

More actions