ActionGorgiasUpdated September 2026

How do I reply to a Gorgias ticket?

Short answer: You can send gorgias reply in Gorgias by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Gorgias Send Gorgias Reply action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Send Gorgias Reply in Gorgias — start free All 6 Gorgias actions

Send Gorgias Reply in Gorgias — start free

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.
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	–

Sample request

{
  "ticket_id": "{{trigger.ticket_id}}",
  "body_text": "{{trigger.body_text}}",
  "sender_email": "e.g. user@example.com",
  "channel": "{{trigger.channel}}"
}

Returns

{
  "id": 9999,
  "body_text": "Thanks",
  "sent_datetime": "2026-05-11T00:00:00Z"
}

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

Triggered by

Apps that pair well as the trigger for Send Gorgias Reply.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Gorgias

2 Google Sheets triggers

HubSpot → Gorgias

18 HubSpot triggers

FAQ

Questions about Send Gorgias Reply.

What does the Send Gorgias Reply action do in Gorgias?

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.

What inputs does Send Gorgias Reply require?

Required: Ticket ID, Reply Body, Sender (agent) email. 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 Send Gorgias Reply support batch operations?

Run Send Gorgias Reply 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