Short answer: Drop the "Gorgias → Create Gorgias Ticket" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | — |
{"subject": "e.g. Quick update","customer_email": "e.g. user@example.com","customer_name": "{{trigger.customer_name}}","channel": "{{trigger.channel}}","via": "{{trigger.via}}"}
{"id": 1234,"status": "open","subject": "Help","customer": {"email": "jane@x.com"}}
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.
Triggered by anything in the catalog. Free tier available. No credit card.