Skip to main content

​
Overview

Once Gorgias is connected, the Dema Agent can work with your helpdesk directly inside a conversation — search and triage support tickets by status, tag, or customer and summarize conversations; pull a customer’s support history for context before outreach; run ad-hoc helpdesk reporting (ticket volume, response and resolution stats, CSAT and satisfaction trends); audit tags, macros, and rules; and add internal notes. Read and write. The agent only acts when you ask it to, and Dema asks you to confirm sensitive changes before they are applied.
The agent can do whatever the authorizing Gorgias user can do — permissions are role-bound. Connect with an appropriately-privileged user so the agent has the access it needs and nothing more.

​
Prerequisites

  • A Gorgias Helpdesk account (the MCP connector is available on all Helpdesk plans, open beta).
  • Your Gorgias subdomain — the “your-brand” part of your-brand.gorgias.com.
  • On Team/Enterprise plans, the Gorgias Owner must add the connector at the organization level first.

​
Connect Gorgias

1

Find your Gorgias subdomain

Log in to Gorgias in a browser. Your subdomain is the “your-brand” portion of your-brand.gorgias.com shown in the address bar.
2

Connect in Dema

In Dema, go to Agents → Settings → Integrations, find Gorgias, and click Connect. Enter:
  • Subdomain — the “your-brand” part of your-brand.gorgias.com.
You are redirected to the Gorgias OAuth screen — click Continue, then Allow Access, then Authorize. No API key is created. Dema marks the integration as Active.
The MCP connector is in open beta. Reads are fully live; some write actions are still rolling out.

​
Troubleshooting

Double-check the subdomain is the “your-brand” part of your-brand.gorgias.com — not your Help Center domain.
On Team/Enterprise plans, the Gorgias Owner must add the connector at the organization level first. Ask your Owner to enable it, then try again.
The agent’s permissions mirror the role of the user who authorized it. Reconnect with a more privileged user if the agent needs broader access.
If you are still stuck, contact support with the error message you see.

​
Additional resources