ActionGorgiasUpdated September 2026
How do I create a Gorgias ticket?
Short answer: You can create gorgias ticket in Gorgias by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Gorgias Create Gorgias Ticket action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
|---|---|---|---|
Subject subject | string | Required | Message subject line. |
Customer Email customer_email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Customer Name customer_name | string | Optional | – |
Channel channel | options | Optional | – |
Via via | options | Optional | – |
First Message Body body_text | string | Required | – |
Tag IDs tags | array | Optional | – |
Sample request
{"subject": "e.g. Quick update","customer_email": "e.g. user@example.com","customer_name": "{{trigger.customer_name}}","channel": "{{trigger.channel}}","via": "{{trigger.via}}"}
Returns
{"id": 1234,"status": "open","subject": "Help","customer": {"email": "jane@x.com"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Create Gorgias Ticket.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Create Gorgias Ticket.
What does the Create Gorgias Ticket action do in Gorgias?
Files a new e-commerce support ticket with subject, message, customer reference, tags. The standard hook for "external support channel → file as Gorgias ticket for unified inbox" workflows.
What inputs does Create Gorgias Ticket require?
Required: Subject, Customer Email, First Message Body. 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 run history shows the failed step with its input and the error message Gorgias returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Create Gorgias Ticket support batch operations?
Run Create Gorgias Ticket inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Gorgias's rate limits.
More actions
Other Gorgias actions.
Action
Get Gorgias Ticket
Returns a ticket by ID with full message history, customer info, channel attribution, current status. The standard lookup for ticket-context workflows.
ActionList Gorgias Tickets
Paginated tickets with filters by status, channel, assignee, tags, time range. For "open tickets matching this pattern" routing workflows or daily-summary digests.
ActionSearch Gorgias Customers
Lookup by email or external ID. Useful for "incoming chat from email X → find existing customer to attribute the ticket" workflows.
ActionSend Gorgias Reply
Posts a public reply or internal note. Routes via the ticket's original channel by default. For AI-assisted responses on routine tickets or for automated acknowledgement workflows.
ActionUpdate Gorgias Ticket
Updates ticket fields — status, assignee, tags. For "auto-tag tickets by content classification" workflows or for "auto-route to specialised team" automation.