Short answer: You can update gorgias ticket in Gorgias by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Gorgias Update Gorgias Ticket action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 | – |
{"ticket_id": "{{trigger.ticket_id}}","status": "{{trigger.status}}","priority": "{{trigger.priority}}","assignee_user_id": "{{trigger.assignee_user_id}}","tags": "{{trigger.tags}}"}
{"id": 1234,"status": "closed"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.