Gorgias Connector — Team Guide

READ-ONLY

Ask Claude to look up support tickets, customers, and conversation history — and to draft replies and triage plans — in plain English. The connector is read-only: nothing Claude does here can change a ticket or reach a customer; you paste and apply its drafts in Gorgias.

Status: Live ✓ Updated: August 5, 2026 Access: read-only — write tools removed Aug 5, 2026 API limit: 40 requests / 20 seconds (auto-retries on 429) Sign-in: your Google work account Questions: David
What it is Connect in 1 minute The safety model How to ask ~50 example prompts Limits & risks Get help / request more Live artifacts Architecture How your data flows

What is the Gorgias connector?

Gorgias is our customer-support helpdesk — where customer emails, chats, and tickets come in and get answered. The Gorgias connector lets Claude read the helpdesk — tickets, messages, customers, search, views, tags, and the team — and turn what it finds into summaries, triage plans, and drafted replies. It is read-only: since Aug 5, 2026 the connector contains no write tools at all, so applying a draft is always a human step done in Gorgias itself.

👀 What it can read

Tickets and their messages, customer records and history, search across the helpdesk, your views, tags, and the team's users — so it can find and summarize anything quickly.

✋ What it can change

Nothing. The six action tools (notes, tags, status, priority, assign, replies) were removed entirely on Aug 5, 2026. Claude drafts; you paste into Gorgias and press the buttons yourself.

🛡️ What keeps it safe

There is no write code in the connector at all — the strongest guarantee possible. A bug, a bad prompt, or even a malicious instruction hidden in a ticket can at worst read; nothing can send, edit, or delete.

Why it matters: CS is repetitive — looking up an order, tagging, triaging, and drafting the same kinds of replies. This connector lets Claude do the legwork in your brand voice while keeping a human firmly in control of anything a customer sees.

Connect it in about a minute

How to connect in three steps Open Settings then Connectors in Claude, find this connector and click Connect, then sign in once with the account noted below. Settings Profile Connectors Data controls 1 · Open Settings → Connectors MM This connectornot connected Connect 2 · Find it · click Connect you@melindamaria.com •••••••• Sign in ✓ 3 · Sign in once — done
In Claude: Settings → Connectors → find it → click Connect → sign in. It’s already added for the team, so this is a one-time, ~1-minute step (see “Which login” below).

The Gorgias connector is already set up in Claude for the team — you just switch it on and sign in. Takes about 30 seconds.

1
In Claude, open SettingsConnectors (or click the + in the message box → Connectors). Find Gorgias in the list — it's already there.
2
Click the + (or Connect) next to Gorgias.
3
When prompted, sign in with your Google work account (your @melindamaria.com email — the same one you use for Gmail & Drive). A personal Gmail won't work.
4
Approve the connection. It shows Connected — then type "In Gorgias, run gorgias_health" — you should see ok: true.
🔑 Which login? You only ever sign in with your Melinda Maria Google work account. You never enter any Gorgias password or key — those are stored securely on our side.
Don't see it in your Connectors list? Ask David — it gets enabled once for the team, then appears for everyone to switch on.

The safety model — read this first

This connector reads a live system your customers feel, so its safety is structural:

1 · Zero write code

The six write tools were removed entirely on Aug 5, 2026 — not switched off, deleted. There is no code path that can change a ticket or email a customer.

2 · Drafts stay in chat

Claude writes reply drafts and triage plans in the conversation. A human copies them into Gorgias — so a person is always the one who presses send.

3 · Same login gate as everything

Only @melindamaria.com / @7ate9.com Google accounts can use it, and the Gorgias API key lives in Cloudflare secrets — never in Claude, never in your browser.

Good habit: for anything a customer will see, read Claude's draft carefully before you paste and send it — check the order facts, the tone, and that it's the right ticket.

How to ask — just say "use Gorgias…"

The connector is named Gorgias. The simplest way to make sure Claude uses it is to mention it in your request:

"Using Gorgias, <your question or task>."

You don't have to memorize tool names — plain English works. A few tips that get great results:

Name the ticket or customer

"…ticket #48213", "…the customer jane@email.com", "…tickets tagged shipping". Concrete anchors = precise actions.

Claude drafts, you send

For customer replies, ask Claude to draft — then you paste the text into Gorgias and press send there. The connector has no send button, so a person is always the one who reaches the customer.

Lean on our brand voice

"…draft a reply in our brand voice", "…warm and on-brand". Claude knows MM's "everyday luxury with a wink" tone for CS.

Chain connectors in one ask

"…look up the order in ShipBob, then draft the Gorgias reply", "…attach the product photo from Canto". See the multi-connector examples below.

~50 example prompts — graded from "just looking" to "real action"

These are grouped into five tiers, from totally safe reads up to power workflows. The label shows the risk level; the line under each shows which connectors get involved. Remember: Claude only drafts — a human always sends.

Read just looks, changes nothing Customer email drafts a reply — you paste & send in Gorgias Power multi-step / multi-connector workflows
👀

Tier 1 — Reading & finding (totally safe)

Read
"Using Gorgias, how many open tickets do we have right now, and how many are unassigned?"
Gorgias
Read
"Using Gorgias, show me ticket #48213 — the full conversation, the customer, and its current status."
Gorgias
Read
"Using Gorgias, list the oldest 10 open tickets so I can see what's been waiting longest."
Gorgias
Read
"Using Gorgias, search for tickets mentioning 'tarnish' in the last 30 days."
Gorgias
Read
"Using Gorgias, pull this customer's record and their full ticket history with us."
Gorgias
Read
"Using Gorgias, what are our current views and tags, and how many tickets sit in each view?"
Gorgias
Read
"Using Gorgias, summarize the top 5 recurring themes in this week's tickets."
Gorgias
Read
"Using Gorgias, which agents have the most open tickets assigned right now?"
Gorgias
🏷️

Tier 2 — Triage & internal notes (Claude drafts — you apply in Gorgias)

Read
"Using Gorgias, pull ticket #48213 and everything we know about the order, and write a summary I can paste into the ticket as an internal note."
Gorgias — read + draft (you paste)
Read
"Using Gorgias, list my open tickets where the customer's last message says the issue is resolved — so I can close them in Gorgias in one pass."
Gorgias — read (you close in Gorgias)
Read
"Using Gorgias, who on the team has the fewest open tickets right now, so I know who should take this one?"
Gorgias — read
Read + plan
"Using Gorgias, review the open queue and propose a triage plan — suggested tag, priority, and owner for every ticket, as a table I can apply in Gorgias."
Gorgias — read + plan (you apply)
🔒 Future capabilities if requested — write commands not active

The connector used to include six action tools — internal notes, tags, status, priority, assignment, and customer replies. They were removed entirely on Aug 5, 2026 so Gorgias is genuinely read-only: today there is no code path that can change a ticket or email a customer.

If the CS team decides it wants Claude to take these actions directly (always preview-and-confirm gated), David can rebuild them. This is what those prompts would look like:

Write — not active
"Using Gorgias, tag this ticket 'shipping-delay' and 'VIP'."
Gorgias — would add tags (confirm-gated)
Write — not active
"Using Gorgias, set ticket #48213 to high priority."
Gorgias — would set priority (confirm-gated)
Write — not active
"Using Gorgias, find all untagged tickets from this week and suggest the right tag for each, then apply them once I OK the list."
Gorgias — would add tags in bulk (confirm-gated)
Write — not active
"Using Gorgias, add an internal note with the order summary, assign the ticket to the right agent, and set it to open."
Gorgias — would note + assign + set status (confirm-gated)

Want these turned on? Say so in #mm-claude or tell David — it's a deliberate re-enable, not a flip of a hidden switch.

✉️

Tier 3 — Customer replies (drafted by Claude — you paste & send)

Customer email
"Using Gorgias, draft a warm, on-brand reply to ticket #48213 letting the customer know their order shipped — don't send, just show me."
Gorgias — drafts reply (you paste & send)
Customer email
"Using Gorgias, draft a reply to this returns question using our returns policy and our friendly voice. I'll review before it goes."
Gorgias — drafts reply (you paste & send)
Customer email
"Using Gorgias, this customer is frustrated about a delay — draft an empathetic, on-brand apology with a clear next step, for my review."
Gorgias — drafts reply (you paste & send)
Customer email
"Using Gorgias, draft replies to the 5 simplest 'where is my order' tickets in the queue, each personalized. Show me all 5 before anything sends."
Gorgias — drafts replies (you paste & send each)
Customer email
"Polish this draft reply for ticket #48213 — warm, on-brand, with the tracking link — and I'll paste it into Gorgias and send it myself."
Gorgias — draft only (you send from Gorgias)
🔗

Tier 4 — Multi-connector: answer with real data

Power
"A customer emailed in Gorgias asking where order #1227070 is. Look it up in ShipBob, get the live tracking, and draft a friendly reply in our brand voice for my review."
Gorgias + ShipBob — drafts reply (you paste & send)
Power
"For this ticket, pull the customer's order detail from Shopify, summarize it, and draft a reply answering their question — I'll paste both into Gorgias."
Gorgias + Shopify — read + drafts (you paste)
Power
"This customer asked what a piece looks like — find the approved product photo in Canto and draft a Gorgias reply with the image linked."
Gorgias + Canto — drafts reply (you paste & send)
Power
"Cross-reference quality: pull the most-returned SKUs from ShipBob and recent complaint tickets from Gorgias, and tell me if any product has both a high return rate and recurring complaints."
Gorgias + ShipBob

Tier 5 — Power workflows & reporting

Power
"Using Gorgias, build me a weekly CS report: ticket volume, top topics, average first-response time, and the worst backlog — as a PDF, with a 3-bullet summary."
Gorgias + PDF
Power
"Using Gorgias, find every open ticket older than 3 days and draft a short status-check reply for each — I'll tag them 'aging' and send from inside Gorgias."
Gorgias — drafts replies (you tag & send)
Power
"Each Monday, using Gorgias, summarize last week's CS themes and any spikes, and post the recap to #cs in Slack as a draft."
Gorgias + Slack — recurring; draft (you confirm)
Power
"Using Gorgias, detect a problem early: if complaint tickets about a single SKU jump this week vs. the prior month, draft an alert to the product team in Slack with the tickets."
Gorgias + Slack — draft alert (you confirm)
Power
"Help me clear the morning queue: review everything open, propose triage (tag + priority + owner for each), draft replies for the straightforward ones, and flag the tricky ones — one plan I can apply."
Gorgias — read + plan + drafts (you apply)
📊

Live artifacts, dashboards & spreadsheets

Analysis
“Create a live artifact: a support pulse dashboard — open tickets by status and priority, refreshed each open.”
Gorgias — live artifact
Analysis
“Build a 'today's queue' board artifact with an oldest-waiting timer at the top.”
Gorgias — queue
Analysis
“Make a spreadsheet (.xlsx) of this month's tickets by tag and channel for the CS review.”
Gorgias — xlsx
Analysis
“Build a repeat-contact tracker artifact — customers with 3+ tickets in 90 days.”
Gorgias — customers
Multi-connector
“Create one artifact joining Gorgias and Loop: the complaint-to-return pipeline, end to end.”
Gorgias + Loop

Limitations, caveats & risk (please read)

Because this connector can take real actions, the safety model leads — here it is in table form, plus the usual notes.

TopicWhat to knowStatus
Customer emails: Claude cannot send themThere is no reply tool anymore. Claude drafts the text in chat; a human pastes it into Gorgias and presses send there. This is the most important thing on the page.Read-only
Replies come from hello@Because you send every reply from inside Gorgias, it always goes out from hello@melindamaria.com — our normal support address.By design
Write tools removed (Aug 5, 2026)The connector used to include six action tools (notes, tags, status, priority, assign, replies). They were removed entirely so Gorgias is genuinely read-only. (Verified live: writes_enabled=false.) Claude still drafts replies and triage plans — you paste and apply them in Gorgias.Read-only
Drafts don't send themselvesClaude can write a perfect reply, but a human always moves it: you paste the draft into Gorgias and press send there. That's by design — nothing Claude does can reach a customer.By design
Confidential dataReal customer names, emails, and order details flow through. Don't paste exports into outside tools, and share reports only with people who should see them.Handle with care
Right ticket, right toneBefore sending a pasted draft, double-check it's the correct ticket and the facts and tone are right. Claude is excellent at our voice, but you're the final eyes.Verify before send

Get help, request features, or report something odd

Something looks wrong?

If a draft references the wrong order, or the connector says it can't reach Gorgias — tell David. Include what you asked and what you got back (a screenshot helps). For anything touching customers, flag it right away.

Want a new capability or a safer default?

Want a recurring report or a new workflow? Send the idea to David. New read tools are quick to add.

Handy built-in you can always run: gorgias_health (is it working? is the account active?). If it ever comes back not-ok, that's the thing to send David.

What is a live artifact and how to share it

Short version: a live artifact is a page Claude builds once and then refreshes every single time you open it — so a dashboard you ask for today is still accurate next month. Here is what one is, and the three ways to get it in front of your team.

📊 NEW — build live artifacts, dashboards & spreadsheets with this connector

A live artifact is a small interactive page Claude builds and saves for you — a dashboard, tracker, or report that pulls fresh data from this connector every time you open it, instead of being a frozen snapshot. In a Cowork session, just ask: “create a live artifact that…” — it lands in your Artifacts list, reusable forever, and its charts and tables refresh themselves on open.

Sharing with the team: artifacts are saved to your Claude account. Three easy ways to share: (1) ask Claude to export a snapshot (PDF, image, or .xlsx) and drop it in Slack; (2) send a teammate the prompt that built it — their copy fills with live data through their own connector sign-in; (3) for a permanent all-team dashboard, that’s the MM Intelligence project on the AI roadmap.

How it works — architecture

Gorgias is read-only by construction — since Aug 5, 2026 the Worker contains zero write code, so the safety story is structural, not procedural. Here's the picture:

Gorgias MCP Connector — Architecture Gorgias helpdesk connector architecture: a Google-gated Cloudflare Worker with 10 read-only tools. No write code exists; Claude drafts text in chat and a human applies it in Gorgias. No database. Gorgias MCP Connector — Architecture (live)Live helpdesk · gorgias-mcp.melindamaria.ai/mcp · Google-gated · 10 tools · all read-onlyREAD-ONLYYou + the teamin Claude (Cowork,Desktop, Web, Code)ask in plain Englishplain EnglishClaudepicks the rightgorgias_ tool &fills in filtersMCP · OAuth 2.1gorgias-mcp — Cloudflare Worker🔐 Google sign-in gateonly @melindamaria.com / @7ate9.com accounts get in10 tools — all read-onlyRead: tickets · customers · messages · search · views/tags/usersWrites: none — the six write tools were removed Aug 5, 2026🛡 Read-only by constructionZero write code in the Worker — it cannot send, tag,assign, or change a ticket. Claude drafts text in chat;you paste and send it from Gorgias yourself.🔑 Gorgias API key (HTTP Basic)in Cloudflare secrets · never visible to Claude or the browser💾 No DB · KV sessions + cache · 40 req/20s, auto-retry on 429Gorgias REST APImelindamaria.gorgias.comtickets · customers · messages · tags · viewsAnswer / drafted actionreads come straight back;reply drafts appear in chatfor you to paste into Gorgias.You / GorgiasOur connectorRead-only boundaryFlowReads: ask → Claude picks a tool → Worker (Google-gated) reads Gorgias live → answer.Replies: Claude drafts the text → you review it → you paste and send from Gorgias yourself. Nothing sends automatically.
Self-hosted on Melinda Maria’s own Cloudflare account at gorgias-mcp.melindamaria.ai/mcp — the same hosting + Google sign-in pattern as our other connectors. All traffic over HTTPS/TLS.

Why read-only?

A helpdesk touches real customers, so this connector keeps zero write code — the strongest safety guarantee there is. Its six action tools were removed on Aug 5, 2026; Claude still drafts replies and triage plans, and a human applies them in Gorgias.

Why live, not synced?

Support tickets change minute to minute. A stored copy would be wrong almost immediately, so Gorgias reads live every time.

Rate-limit-aware & hosted like our others

Gorgias caps requests at 40 per 20 seconds; the connector auto-retries on a 429 so it never disrupts the helpdesk. It runs on our own Cloudflare account behind the same Google sign-in as every MM connector, with the API key kept server-side.

How your data flows (the 30-second version)

You don't need to understand the plumbing to use it — but here's the simple picture:

When you ask it to look something up

e.g. "what's the latest on this ticket?" → Claude reads Gorgias and answers. Nothing changes.

When you ask it to do something

e.g. "suggest a tag and draft a reply" → Claude proposes the tag and writes the draft; you apply the tag and send the reply inside Gorgias. Nothing Claude does here can change a ticket.

Everything happens behind a secure sign-in. The connector only works for people signing in with a @melindamaria.com or @7ate9.com Google account. Real customer details flow through — treat anything you export as confidential.
Melinda Maria · Gorgias Connector Team Guide · August 5, 2026 · read-only (write tools removed) · 10 tools · you send replies from Gorgias itself · sign in with your Google work account.
Questions, anomalies, and feature requests → David. This guide is updated as the connector grows. · ← Back to all connectors
The Next Evolution of Melinda Maria. Every corner of the business, one question away.