Short answer: Drop the "Gorgias → Send Gorgias Reply" 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 |
|---|---|---|---|
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. |
Reply Body body_text | string | Required | — |
Sender (agent) email sender_email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Channel channel | string | Optional | — |
{"ticket_id": "{{trigger.ticket_id}}","body_text": "{{trigger.body_text}}","sender_email": "e.g. user@example.com","channel": "{{trigger.channel}}"}
{"id": 9999,"body_text": "Thanks","sent_datetime": "2026-05-11T00:00:00Z"}
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.