Connect Gorgias to Rig

    Three values from Gorgias and your support data is in the warehouse: tickets, message content, satisfaction surveys and tags, joinable to the orders and customers they are about. Gorgias has no scope model, so the only thing to get right is who creates the key.

    Requirements
    Account owner permission in Gorgias
    Time required
    2 mins

    Before you start

    • Account owner permission in Gorgias. Creating a REST API key requires it, and an agent or admin account will not see the option.
    • By the end you will have three values for Rig: your subdomain, the account owner's email, and the API key.

    Create an API key

    1. In Gorgias, go to Settings → REST API.
    2. Click Create API key and copy the key.
    3. Note the email address of the account owner whose key this is. Gorgias authenticates with the email and key together, so the pair has to match.

    There are no scopes to choose
    Gorgias has no permission model on API keys: the key inherits the account owner's access, which is why it has to be an owner. If you are hunting for a scopes screen, there is not one.

    Connect it in Rig

    1. In Rig, open Connections and go to Sources & actions.
    2. Search for Gorgias and open the card.
    3. Gorgias subdomain: just the first part of your Gorgias URL. For acme.gorgias.com, that is:
      acme
      Pasting the full URL also works, and Rig will trim it for you.
    4. Account owner email: the address the key belongs to.
    5. API key: paste the key.
    6. Click Test, then Sync.

    What Rig pulls in

    Gorgias lands in its own gorgias schema:

    • Tickets and their messages, including the body text rather than just counts
    • Customers
    • Satisfaction surveys
    • Tags, views, macros and integrations
    • Users, your agents, for per-agent analysis

    Message bodies are trimmed of the heavy parts Gorgias attaches to every message: raw HTML, headers, actions, intents and attachment metadata. That keeps rows about two-thirds smaller without losing the text anyone would actually read or analyse.

    Why the first sync is slow

    The Gorgias API has no server-side date filter. There is no way to ask it for tickets changed since yesterday, which is the mechanism every other connector uses to stay quick. We confirmed this by probing the API directly: every date-filter parameter it accepts in principle returns an error in practice.

    The practical effect is that a large history has to be walked page by page. For a busy support desk with a few million messages, a first load runs for hours. Ongoing syncs are much lighter.

    Rig deliberately runs at half speed here
    Gorgias caps the account API at roughly 40 calls per 20 seconds, and that budget is shared with your live support agents. Rig holds itself to 60 calls a minute so a backfill never slows down the people answering tickets. We could go faster; it would come out of your team's response times.

    If you have a very large Gorgias history, tell us before you start. We run the initial message backfill separately, off your production sync, so it neither competes with your agents nor blocks the rest of your data landing.

    Troubleshooting

    • Authentication fails: the email and key must be the pair Gorgias issued together. A key created by one person and an email belonging to another will not authenticate.
    • There is no Create API key button: you are not signed in as the account owner. Gorgias restricts REST API keys to owners.
    • Your agents report Gorgias feeling slow: tell us, and we will pause the backfill. The API budget is shared, and live support wins.
    • Ticket counts look short during the first load: the backfill is still walking history. Counts settle once it finishes.

    Was this guide helpful?