--- title: Gorgias slug: gorgias docTags: createdAt: 2026-09-02T18:57:51.356Z --- Gorgias is a customer support and helpdesk platform built for ecommerce brands, unifying email, chat, social, and SMS conversations into one inbox. Connecting Gorgias to Chord brings your support history into the same warehouse as your orders, customers, and marketing data, so ticket volume, response times, and CSAT can be analyzed alongside everything else your brand tracks. ## What Chord ingests from Gorgias Chord pulls 12 datasets from your Gorgias account. Each dataset becomes its own table in your Chord Snowflake schema. - **Tickets.** Every support ticket, including channel, subject, status, assignment, and tags. - **Messages.** Every message tied to a ticket, with sender and timestamp. - **Customers.** Contact records from Gorgias, including name and email. - **Satisfaction surveys.** CSAT ratings and comments left on resolved tickets. - **Tags.** The tag library used to label and filter tickets. - **Users.** Agent accounts in your Gorgias workspace. - **Teams.** The team groupings tickets can be assigned to. - **Integrations.** The third-party apps and channels connected to your Gorgias account. - **Macros.** Saved canned responses. - **Rules.** Automation rules configured in Gorgias. - **Views.** Saved ticket views and filters. - **Events.** Account activity events, pulled with a 30-day lookback on the first sync. Once your connector is live, ask your Chord contact to enable the Gorgias Tickets explore and the prebuilt Gorgias Support Showcase dashboard in Analytics. :::hint{type="info"} **Heads up:** Tickets, messages, customers, and events sync incrementally, picking up only what changed since the last run. Satisfaction surveys, tags, users, teams, integrations, macros, rules, and views resync in full every run. ::: ## Generate a Gorgias API key You'll need three things from Gorgias: your account subdomain, the email address of the Gorgias user the key belongs to, and a REST API key generated from that user's account. There's no scope picker. One key grants access under that user's own permissions. :::hint{type="warning"} **Heads up:** Only account owners and admins can generate a REST API key in Gorgias. If you're on another role, ask an admin on your team to create the key or grant you access first. ::: 1. Log in to your Gorgias helpdesk. 2. Click the **Settings** icon in the bottom-left corner, then go to **Account → REST API**. 3. Under **Password (API Key)**, click **Create API Key**. The key is generated immediately and shown alongside your base API URL and username. 4. Copy the key. It stays visible on the REST API page, so you can come back for it later. The **Reset** button next to it generates a new key and invalidates the old one immediately, so only use it when you mean to rotate. 5. Note the subdomain from your Gorgias URL (the part before `.gorgias.com`) and the email address of the account you generated the key under. You'll need both to connect in Chord. ## Connect the key in Chord 1. Open Chord Hub and go to **Data Sources → Add Source**. 2. Pick **Gorgias** from the data source list. 3. Enter your Gorgias account subdomain in the **Account Subdomain** field. Use just the prefix, for example `yourbrand` for `yourbrand.gorgias.com`, not the full URL. 4. Enter the email address of the Gorgias user who owns the key in the **User Email** field. 5. Paste the key into the **API Key** field. 6. Click **Save**. Chord makes a test call against `https://.gorgias.com/api/account` to confirm the credentials work. 7. The first sync kicks off automatically and backfills your ticket, message, and customer history. From there, Gorgias syncs on your tenant's standard ingestion schedule. ## Troubleshooting **What does the validate step actually check?** Chord sends a `GET` request to `https://.gorgias.com/api/account` using HTTP Basic auth with the email and API key you entered. A `200` response means the credentials are valid and the connection saves. No ticket or customer data is pulled or stored at this stage. It's a connectivity check only. **The validate step failed. What now?** Check that the subdomain field holds just the prefix, `yourbrand`, not the full URL and not a trailing slash. Confirm the email matches the Gorgias user the key was generated under, not a different teammate's account. If both look right, someone may have clicked **Reset** in Gorgias since you copied the key. Open **Settings → Account → REST API**, copy the current value, and paste it into Chord. **Do Gorgias API keys expire?** No. A key stays valid until someone clicks **Reset** next to it in Gorgias. That invalidates the old key at once, and syncing stops until the new one is saved in Chord. **How do I rotate the key?** In Gorgias, go to **Settings → Account → REST API** and click **Reset** next to **Password (API Key)**. The old key stops working the moment the new one appears, so paste the new value into the same Gorgias credential entry in Chord Hub and click **Save** right away to keep the gap short. **How does Gorgias data connect to my order and customer data?** Chord matches Gorgias contacts to your store's customer records by email, lowercased and trimmed on both sides, inside the Gorgias Tickets explore. A contact with no email on file, or one who's never placed an order, won't have a match. Gorgias doesn't carry an order reference, so there's no direct ticket-to-order join, only the email-based customer match. The explore includes a **Has Matching OMS Customer** field under the Customer group, so you can filter to matched contacts or see unmatched tickets as a known gap instead of blank customer attributes. "No" covers both contacts who never ordered and contacts whose Gorgias record has no email to match on. **Why does my raw ticket count look higher than the support volume I'd expect?** Not every row in the tickets table is a genuine support request. Review-platform notifications, social mentions, and other automated messages can land in Gorgias as tickets alongside real customer conversations, depending on how your team has Gorgias configured. If you're using ticket counts as a proxy for support volume, check the `channel` and `via` fields on each ticket to see how it actually arrived, rather than relying on total row count alone. :::hint{type="info"} **Need help?** If you hit a credential or connectivity issue you can't resolve on the platform, reach out to [help@chord.co](mailto\:help@chord.co) with the exact error message. We'll trace the request and tell you what's failing. :::