Gorgias
Manage Gorgias tickets, customers, messages, tags, views and satisfaction surveys.
About
Gorgias ships in the w6w first-party pack. It declares 22 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.gorgias- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Support
Overview
Gorgias is a helpdesk built for ecommerce. This app covers the ticket lifecycle from a workflow — creating, updating, fetching, listing and deleting tickets, and posting both internal notes and customer-facing replies to keep a conversation moving without an agent opening Gorgias directly.
Customers can be created, updated, fetched, listed and deleted, so a workflow can look up or create the requester behind a ticket. Tags can be listed, created and deleted, and can be attached to a ticket at creation time. Views (Gorgias’s saved ticket filters) can be listed and retrieved so a workflow can react to the same queues an agent works from. Satisfaction surveys — CSAT scores tied to a ticket and customer — can be listed, created, fetched and updated.
A fit for routing an external event — an order issue, a form submission, an alert from another system — into a new Gorgias ticket, updating tickets as a workflow progresses, or syncing customer data and CSAT results between Gorgias and the rest of a support stack.
Build with Gorgias
Three routes to the same 22 actions. The Workflow tab is generated from Gorgias's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Satisfaction Surveys
survey-get-many List satisfaction surveys, optionally scoped to one ticket.
Update Satisfaction Survey
survey-update Record or change a satisfaction survey's score and comment.
List Tickets
ticket-get-many List tickets, newest first by default. Use the filters to narrow the set.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Gorgias's real ids.
{
"manifestVersion": "2",
"name": "gorgias-example",
"steps": [
{
"id": "customer-get",
"uses": {
"app": "io.w6w.gorgias",
"action": "customer-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"customerId": "<customerId>"
}
}
]
}Here are some of the things you can do
-
Get Customer
readcustomer-get -
Create Customer
performcustomer-create -
List Customers
searchcustomer-get-many -
Update Customer
performcustomer-update -
List Messages
searchmessage-get-many
+17 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Gorgias, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Gorgias. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "customer-get",
payload: {
customerId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action customer-get --payload '{"customerId":"<value>"}'Give an AI agent Gorgias — without giving it Gorgias's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.gorgias#customer-get",
"input": {
"customerId": "<customerId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Gorgias connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Gorgias's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Gorgias itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Gorgias declares its own checks, so its health is a property of the app rather than something the host guesses at.
Gorgias platform status
Open incidents on status.gorgias.com's Atom history feed. Unauthenticated and unsigned; fetched and parsed by the host.
API call-limit headroom
Leaky-bucket headroom from `X-Gorgias-Account-Api-Call-Limit`, reported as calls still available before throttling.
Account domain reachable
Unauthenticated request to this connection's Gorgias domain. A 401 passes — it proves the account is serving; credential validity is the `auth:*` check's job.