Gorgias

What it does

The Gorgias node connects your flow to Gorgias, letting you read and manage support tickets and customer records directly from a Syncaut automation — for example, automatically opening a ticket when an order has an issue, or replying to a customer once a refund is processed.

Setup

Before using this node, you'll need a Gorgias credential connected:

1. In Gorgias, go to Settings → REST API → Create new key.

2. In Syncaut, add a new Gorgias credential using your Gorgias subdomain (the part before .gorgias.com), your account email, and the API key you just created.

Note: unlike single-API-key integrations (e.g. DeepSeek, Mailchimp), Gorgias needs three pieces of information together. The credential is stored as encrypted JSON in exactly this shape:

{
  "subdomain": "acme",
  "email":     "[email protected]",
  "apiKey":    "the-api-key-from-gorgias-settings"
}

Make sure all three fields are filled in when creating the credential — a credential missing any one of subdomain, email, or apiKey won't be usable by this node.

Once connected, the credential will be available to select from any Gorgias node.

What's stored in the credential

A Gorgias credential holds three pieces of information:

Field Description subdomain The part of your Gorgias URL before .gorgias.com (e.g. acme for acme.gorgias.com) email The account email tied to the API key apiKey The API key generated in Gorgias

These are stored encrypted and only decrypted at the moment the node runs. Behind the scenes, Syncaut combines your email and API key into a Basic Auth header to authenticate each request to Gorgias — you never need to handle the authentication yourself.

If the selected credential is missing, or doesn't contain all three of subdomain, email, and apiKey, the step will fail immediately with a clear error rather than attempting the request — re-adding the credential with all three fields filled in resolves this.

Configuration

The dialog walks through three steps:

1. Connect — pick a Step name and the Gorgias account (credential) to use.

2. Action — choose what you want to do (see the full list below).

3. Parameters — fill in the fields for the chosen action, either as a simple form or, for advanced cases, as raw JSON.

Available actions

Tickets

Action Required fields Optional fields Get tickets — Filter by status, filter by customer ID, limit Get ticket Ticket ID — Create ticket Subject, customer email, initial message Customer name, tags (comma-separated), priority Update ticket Ticket ID Status, priority, tags (comma-separated — replaces existing tags), assign to user ID Close ticket Ticket ID — Reply to ticket Ticket ID, message From agent? (true/false), channel

Customers

Action Required fields Optional fields Get customers — (none exposed in the form — returns up to 30 by default) Get customer Customer ID — Create customer Email Name, external ID (e.g. a Shopify customer ID) Update customer Customer ID Name, email, external ID

Form vs. JSON mode

For actions that take parameters, you can switch between a simple form and a raw JSON editor using the toggle in the Parameters step. JSON mode is useful if you need to pass a field that isn't exposed in the form (for example, a specific fromEmail or bodyHtml on a reply), or if you prefer writing the payload directly. Use {{variableName}} inside the JSON to reference data from earlier steps.

How to reference the output

The result is stored under the Step name you chose, with two fields available:

Reference Returns {{result.data}} The raw response from Gorgias for the action you ran {{result.action}} The action that was performed

(Replace result with whatever Step name you chose.)

Notes & troubleshooting

• For Reply to ticket, leaving From agent? blank sends the reply as if it came from an agent (the default is true) — type false explicitly if you need the message recorded as coming from the customer instead.

• Get customers doesn't expose filtering or pagination in the form — it always returns the first 30 customers. If you need to page through more, you'll need to use JSON mode and pass a cursor value yourself.

• Tags on Update ticket replace the ticket's existing tags rather than adding to them — if you want to keep existing tags, include them again in the comma-separated list along with any new ones.

• Required fields that are missing (e.g. submitting Create ticket without a customer email) will cause the step to fail immediately rather than retry, so double-check required fields are filled in or correctly referencing a variable that resolves to a real value.

• Credentials are tied to the account that created them — a Gorgias credential added under your login won't be selectable by a teammate using their own account unless they add their own credential.