Major

Gorgias AI Agent: API, Apps and Governed Workflows

Explore Gorgias AI Agent, seven verified API operations and governed support workflows on Major, with durable review queues, scoped connectors and human approval.

Ritvij GautamUpdated
Major x Gorgias logo lockup

Gorgias AI Agent is Gorgias's native assistant for ecommerce support and shopping conversations. This guide explains its capabilities, the Gorgias API, and where Major adds cross-system judgment, durable review queues and human approvals.

On Major, agents build deterministic apps for repeatable work, then reserve reasoning for exceptions that require judgment.

What Gorgias is and who relies on it

Gorgias is an ecommerce helpdesk where support teams manage customer conversations alongside order context. Its AI Agent documentation describes work spanning product discovery, returns, cancellations, missing items and shipping updates across email, chat, SMS and social channels.

For a customer experience manager, the job is keeping those conversations moving without losing the order history behind them. A fulfillment operations manager needs a different view: which delayed orders deserve proactive outreach, which already have an open ticket, and which promises need warehouse confirmation.

An ecommerce risk manager may use a support ticket to coordinate an ambiguous order review while keeping the actual hold or release decision under authorized control. These jobs share evidence, but they do not share identical permissions.

Major gives these teams a deterministic app that holds exception records, evidence snapshots and approvals. An agent assesses conflicting evidence or drafts a handling summary. The workflow gathers records and routes the result, while Gorgias remains the place support staff work the conversation.

Gorgias AI Agent and its built-in capabilities

The native AI Agent has two roles: Support agent for post-purchase questions and Shopping assistant for pre-purchase conversations. Gorgias provides knowledge sources, skills, tone settings and opt-in Actions that can change records in connected tools, such as canceling an order or updating a shipping address.

Skills bundle conversation intents with instructions. Knowledge can include help center articles, website content, documents and Shopify data. Gorgias also documents image understanding, human handover, visible reasoning and feedback on responses. These are substantial capabilities, not merely suggested replies.

The automation documentation index also lists Gaia, currently labeled Beta, as a coaching agent that identifies setup gaps and drafts improvements for review. Flows and Order Management provide scripted self-service alongside the AI features.

Major adds value when the process needs a persistent exception record spanning Gorgias, fulfillment evidence and another team's approval. Do not rebuild ordinary order-status conversations just to introduce another agent. Give the native assistant clear conversation ownership and use a Major agent for the cross-system assessment, with the app preserving evidence and the workflow enforcing action boundaries.

How Gorgias connects to Major

Gorgias connects through Major's Pipedream connector. There is no native Gorgias connector. The catalog identifies the OAuth app connection; do not describe it as a direct, built-in Gorgias integration or assume every documented API operation is already exposed as a connector action.

IT sets up the connection once, checks its available operations and grants only the access the process needs. Credentials stay in Major's connector vault, never in app code, prompts or review records. Apps, agents and workflows reuse that centrally governed connection under SSO, role-based access control and audit logging.

The upstream REST address uses the account domain, as shown in the ticket reference. Its authentication details matter when evaluating connector permissions, but a writer or operator should not paste raw keys into an agent instruction.

Major orchestrates Gorgias; it never replaces it. Keep ticket handling and customer delivery in Gorgias, managed process state in the Major app, and consequential writes behind the workflow's approval policy. Confirm operation coverage before committing a build to production.

Gorgias API guide for apps, agents and workflows

Authentication, pagination and operating limits

Gorgias authentication distinguishes private apps using API keys from public apps, which must use OAuth2. Private API keys use HTTP Basic Auth with the user's email and API key, and inherit that user's permissions.

For OAuth, request documented scopes such as tickets:read and customers:read for evidence gathering, adding tickets:write only for approved ticket or message changes. The offline scope supports refresh tokens. These names describe Gorgias permissions, not a promise that the installed connector requests exactly that set. Inspect the actual grant.

Pagination uses cursor and limit, with the next cursor returned in response metadata. The default page size is 30. Ticket listing and message listing allow up to 100 per page. Store checkpoints rather than repeatedly reading the entire account.

Rate limits are 80 requests per 20 seconds for OAuth2 apps and 40 for API-key integrations. Enterprise accounts use those counts within 10 seconds. A 429 means throttling. Watch X-Gorgias-Account-Api-Call-Limit and honor Retry-after, measured in seconds.

HTTP integrations support configurable methods, headers and ticket triggers. The Integration object includes ticket creation, updates, new messages and handover events. The pages reviewed do not document a universal webhook signature scheme or retry schedule. Configure a shared secret header, validate it at the receiver and reconcile missed events instead of assuming signed, guaranteed delivery.

For testing, Gorgias documents developer sandbox access, requiring a draft app and coordination with its technology partnerships team. Start with synthetic records and private notes, not real customer replies.

GET /api/tickets

List tickets with filters including customer ID, external ID or a saved view. Explicitly exclude trashed tickets when the process should consider only active records.

  • App: Populate an exception queue with ticket references and timestamps.
  • Agent: Read the selected customer's prior cases to assess whether a new complaint repeats an unresolved issue.
  • Workflow: Page through a view on a schedule and checkpoint the scan for reconciliation.

GET /api/tickets/{id}

Retrieve the current ticket before presenting evidence or changing its handling. A fresh read prevents an old snapshot from overwriting newer support work.

  • App: Show the latest support status beside the stored recommendation.
  • Agent: Assess whether a teammate's recent intervention changes the proposed next step.
  • Workflow: Refresh the record before executing an approved action and stop if its context changed.

POST /api/tickets

Create a ticket with initial messages and optional assignment, priority and external reference. Initial message configuration matters because ticket creation is not inherently a draft-only operation.

  • App: Save the returned ticket ID against one order exception.
  • Agent: Prepare a concise subject and evidence summary for the receiving support team.
  • Workflow: Create one internal review ticket after deduplication, using an explicitly private initial note rather than accidentally sending outreach.

PUT /api/tickets/{id}

Update properties such as assignment, status or priority on an existing ticket. Restrict the payload to fields the process is authorized to change.

  • App: Display intended and completed assignment side by side.
  • Agent: Recommend escalation priority from the complaint and order evidence.
  • Workflow: Apply an allowed routing update after validation, requiring approval for sensitive status changes.

GET /api/customers/{id}

Retrieve a customer record for identity and support context. The reference documents a 301 when a customer has been merged, so account for identity changes.

  • App: Maintain the approved mapping between the support customer and commerce customer.
  • Agent: Summarize relevant customer context without treating a matching display name as proof of identity.
  • Workflow: Refresh the mapping and route ambiguous or merged identities for reconciliation before any outreach.

GET /api/messages

List paginated messages, optionally filtered by ticket ID and ordered by creation time. Use this current endpoint rather than the deprecated ticket-specific listing operation.

  • App: Preserve references to the evidence used for a recommendation.
  • Agent: Read the conversation to avoid drafting a promise that contradicts an earlier reply.
  • Workflow: Fetch additional pages as needed, with a bounded context window and a durable checkpoint.

POST /api/tickets/{ticket_id}/messages

Create a private note or a customer-facing message. Gorgias documents asynchronous sending: message creation does not prove delivery, and omitting the sent timestamp can initiate sending.

  • App: Hold the draft, reviewer identity, approved text and returned message reference.
  • Agent: Draft the explanation and flag unsupported delivery promises.
  • Workflow: Write an explicitly configured internal note, or send the exact approved customer reply and track its subsequent delivery state.

Gorgias automation use cases on Major

Shopify fraud-risk review with Gorgias

A completed risk result should lead to evidence review, not an automatic fulfillment decision based on a summary alone.

  • App: Store order evidence, risk result, recommendation and final human decision.
  • Agent: Weigh the risk signal against order history and explain a recommended hold, release or escalation.
  • Workflow: Find an existing review through GET /api/tickets, then use POST /api/tickets for an ambiguous case. Keep hold, release and cancellation with an authorized person.

Shopify and ShipStation delay outreach

Combine fulfillment evidence with the conversation already underway so a proactive message does not contradict support.

  • App: Track the order-to-shipment match, promised window, evidence age and outreach status.
  • Agent: Assess whether the delay warrants contact and draft a factual explanation.
  • Workflow: Read GET /api/messages, create an internal review ticket through POST /api/tickets, and request approval before customer delivery.

Gorgias and Intercom VIP escalation

This is a proposed cross-team pattern, not a published implementation guide. Use it only where both teams deliberately share responsibility.

  • App: Match customer IDs and track the receiving conversation reference and escalation owner.
  • Agent: Draft a handling brief that distinguishes verified order history from unconfirmed requests.
  • Workflow: Read GET /api/customers/{id} and GET /api/tickets/{id}, route a reviewed handoff to Intercom, and record acknowledgment before changing Gorgias ownership.

Across all three patterns, connector permissions and policy checks constrain the action. The agent supplies judgment, the workflow carries it through approved steps, and the app prevents the process from disappearing when a run ends.

Build the Gorgias architecture on Major

Gorgias and Shopify evidence flowing through a Major workflow, agent, approval policy and stateful app

Gorgias exception architecture with judgment and durable review state

Build a narrow exception process before adding more channels. The app should hold one record per business exception, not one record per model invocation, so retries and human follow-up attach to the same case.

  1. Connect Gorgias through the cataloged Pipedream connection and authorize the other systems separately.
  2. Build an app with managed tables for evidence, recommendations, approvals and external record references. Add a review queue showing stale evidence and blocked actions.
  3. Configure a workflow trigger or schedule to fetch records, normalize identifiers and check for an existing case.
  4. Give the agent scoped evidence access and a clear judgment task: assess the exception, cite the facts and draft the proposed handling.
  5. Route the proposal through deterministic permission checks and any required human approval, then record the outcome in the app.

The agent can build reusable lookup and validation software once, then run that app on subsequent cases. Reason once. Run forever. The model still handles interpretation; code handles repeated joins, checkpoints and allowed state transitions.

A worked delay-review example with numbers

For example, suppose an ecommerce operations team reviews 200 possible shipment delays each week. This is illustrative planning arithmetic, not a customer result or a performance promise.

Before the build, assume each review takes six minutes: locating the order, checking shipping evidence, finding prior support messages and writing a draft. That is 200 multiplied by six, or 1,200 minutes, equal to 20 hours weekly.

After the build, suppose the app assembles evidence and the agent drafts the handling summary. If a person spends two minutes reviewing each case, that is 400 minutes. Add an assumed 100 minutes for exceptions, reconciliation and queue supervision: 500 minutes, or eight hours and 20 minutes.

The illustrative difference is 700 minutes, or 11 hours and 40 minutes weekly. Measure actual review effort before using that figure in a business case.

One order enters the app, receives an evidence snapshot, gets an agent recommendation and reaches a named reviewer. If the warehouse has not confirmed timing, the reviewer edits out the delivery promise. The workflow sends only the approved wording and records the resulting message reference.

Governance, approvals and failure handling

Major agent draft routed to private Gorgias notes or human-approved customer replies with an app audit record

Approval gates separate internal notes from consequential customer actions

Allow straight-through processing only for explicitly permitted internal work, such as adding a private evidence note. Require a person for refunds, order release, cancellation, sensitive escalation or external promises. An agent must never infer approval from a customer asking for an action.

Use SSO and RBAC to separate evidence readers, reviewers and connector administrators. Record the input snapshot, recommendation, policy version, reviewer, exact approved payload and resulting external ID. Treat ticket text as untrusted content, not instructions that can expand connector permissions.

For rate limiting, use the documented response headers, bounded backoff and a visible retry queue. Deduplicate with business identifiers in the app; do not assume an external reference is a vendor-enforced idempotency key.

After an uncertain write timeout, reconcile before resending. A created message may still be awaiting asynchronous delivery. Re-read the conversation, handle identity changes, and stop stale approvals when the customer or shipment evidence changes. Suppress events generated by the workflow's own notes so ticket updates cannot create a feedback loop.

Gorgias AI Apps, Agents and Workflow Automations

Every published Major use case that works with Gorgias, newest first. Each one names the Gorgias API objects involved and shows the app, agent and workflow split.

  • Automate Shopify-ShipStation Delay Alerts with AI: A Shopify-ShipStation connection moves orders and tracking. Add a governed workflow that spots shipments falling behind and lets support review proactive customer updates before complaints arrive.

Frequently asked questions

What is Gorgias AI Agent?

Gorgias AI Agent is Gorgias's native ecommerce assistant for support and shopping conversations. It uses configured knowledge, skills and actions to answer questions, perform permitted tasks and hand conversations to people.

Does Major replace Gorgias AI Agent?

No. Major adds deterministic apps, agent judgment and governed workflows around Gorgias and other business systems. Keep Gorgias's native AI handling the conversations it is configured to own.

Does Major have a native Gorgias connector?

No. Gorgias connects through Major's Pipedream connector. IT configures the connection centrally and controls access through the connector vault and Major permissions.

How does Gorgias API authentication work?

Private apps use HTTP Basic Auth with a user's email and API key. Public apps must use OAuth2. OAuth scopes distinguish ticket reads and writes, customer access and other resources; API keys inherit their user's permissions.

Can a Gorgias API message be kept internal?

Yes. The create-message reference documents an internal-note channel and private notes that are not sent to customers. Creating a public message can initiate delivery, so store drafts in the Major app until approval and explicitly configure internal notes.

What are Gorgias API rate limits?

The public reference lists 80 requests per 20 seconds for OAuth2 apps and 40 per 20 seconds for API-key integrations. Enterprise accounts use the same counts over 10 seconds. Watch the documented call-limit header and honor Retry-after on throttling.

Sources

The official Gorgias pages below support the product and API claims in this guide. Authentication and scopes are separate references because an API key's inherited user permissions differ from an OAuth grant. Endpoint pages establish the HTTP methods, paths and request semantics used above; verify them again when implementing a production write.

Start building on Major

Build a Gorgias exception app that holds the evidence, gives an agent a bounded judgment task and routes customer-facing changes through human approval.

About the author

Ritvij Gautam is Head of Growth at Major.

Last reviewed November 19, 2026 by Ritvij Gautam.

Frequently asked questions

What is Gorgias AI Agent?
Gorgias AI Agent is Gorgias's native ecommerce assistant for support and shopping conversations. It uses configured knowledge, skills and actions to answer questions, perform permitted tasks and hand conversations to people.
Does Major replace Gorgias AI Agent?
No. Major adds deterministic apps, agent judgment and governed workflows around Gorgias and other business systems. Keep Gorgias's native AI handling the conversations it is configured to own.
Does Major have a native Gorgias connector?
No. Gorgias connects through Major's Pipedream connector. IT configures the connection centrally and controls access through the connector vault and Major permissions.
How does Gorgias API authentication work?
Private apps use HTTP Basic Auth with a user's email and API key. Public apps must use OAuth2. OAuth scopes distinguish ticket reads and writes, customer access and other resources; API keys inherit their user's permissions.
Can a Gorgias API message be kept internal?
Yes. The create-message reference documents an internal-note channel and private notes that are not sent to customers. Creating a public message can initiate delivery, so store drafts in the Major app until approval and explicitly configure internal notes.
What are Gorgias API rate limits?
The public reference lists 80 requests per 20 seconds for OAuth2 apps and 40 per 20 seconds for API-key integrations. Enterprise accounts use the same counts over 10 seconds. Watch the documented call-limit header and honor Retry-after on throttling.