Gorgias
BUSINESS · CRM & SUPPORT
Tickets, their messages, views, customers, and macros in the helpdesk they connected.
Connecting Gorgias in practice
Gorgias runs a leaky bucket over a 20-second window and gives an OAuth2 app twice the room of an API-key integration: 80 requests per 20 seconds against 40. Enterprise accounts get the same two figures over a 10-second window, so identical code runs twice as fast on one helpdesk as on another, and the budget is per account rather than per credential.
Scopes that draw scrutiny
customers:readGorgias’s own description: email address, first name, last name, language, notes, and data received via integrations such as Shopify — so it reaches whatever the store has synced in.customers:writeEdits the customer record itself, which is the object other Gorgias automations key off.users:writeUsers are the helpdesk’s own agents, so this changes staff accounts rather than customer data.integrations:writeChanges the connected integrations, which is how data reaches the helpdesk in the first place.
Rate limits
- OAuth2 apps: 80 requests in a 20-second window.
- API key integrations: 40 requests in a 20-second window.
- Enterprise accounts: the same figures measured over a 10-second window.
- Leaky bucket, so capacity replenishes continuously instead of resetting at a boundary.
- 429 Too Many Requests with Retry-After in seconds, plus X-Gorgias-Account-Api-Call-Limit reporting used against limit, for example 10/80.
Who has to approve
A public app is submitted to Gorgias’s tech partnership team, which reviews that it works properly and is aligned with their expectations before it appears in the in-product App Store or the public listing. Gorgias publishes no timeline and contacts the developer with the result; a rejected app gets feedback rather than a queue position.
Worth knowing
- The limit header is named X-Gorgias-Account-Api-Call-Limit because the bucket is per account: every integration on one helpdesk shares it, so your own traffic is not the only thing that exhausts it.
- Moving a private API-key integration to a public OAuth app doubles the budget, which makes an authentication migration a throughput change as well.
- Some ticket custom fields are system-managed — Gorgias names AI Agent Outcome and AI Intent — and can only be deleted by Gorgias internal apps, so an agent’s cleanup pass will fail on them.
- Audit log event retention is capped at 12 months, so anything an integration needs to prove about its own past writes has to be mirrored elsewhere.
Checked against Gorgias rate limits (2026-09-29), OAuth2 scopes (2026-09-29), Submit app for review (2026-09-29), Audit log retention changelog (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Gorgias behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.