Update Gorgias Ticket: 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
Ticket ID ticket_id	string	Required	The Ticket ID assigned by Gorgias. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Status status	options	Optional	—
Priority priority	options	Optional	—
Assignee User ID assignee_user_id	string	Optional	—
Tag IDs tags	array	Optional	—

Sample request

{
  "ticket_id": "{{trigger.ticket_id}}",
  "status": "{{trigger.status}}",
  "priority": "{{trigger.priority}}",
  "assignee_user_id": "{{trigger.assignee_user_id}}",
  "tags": "{{trigger.tags}}"
}

Returns

{
  "id": 1234,
  "status": "closed"
}

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

FAQ

Questions about Update Gorgias Ticket.

What does the Update Gorgias Ticket action do in Gorgias?

Updates ticket fields — status, assignee, tags. For "auto-tag tickets by content classification" workflows or for "auto-route to specialised team" automation.

What inputs does Update Gorgias Ticket require?

Required: Ticket ID. 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 Update Gorgias Ticket support batch operations?

Yes. Run Update Gorgias Ticket 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