The complete guide to AI agent Gorgias integration (2026)

Disclosure: This article is published by eesel AI, a competitor of Gorgias. Read Gorgias’s own materials alongside this guide.

An AI agent connected to Gorgias can help with recurring questions, ticket classification, and reply drafting. The important choice is which agent you are configuring and what it is allowed to do.

Gorgias has a native AI Agent. eesel provides a separate teammate that connects to Gorgias and can be operated through eesel CLI. This guide explains both paths, then walks through a CLI setup that starts with internal notes for human review.

Native Gorgias AI and an eesel teammate are separate options

Gorgias’s AI Agent documentation describes two skillsets: Shopping Assistant and Support Agent. They cover pre-purchase recommendations and post-purchase work such as tracking, edits, returns, and subscription management.

The documented requirements include an AI Agent subscription and a connected Shopify store. The page lists knowledge sources, Guidance, Actions, test conversations, and deployment controls. Check those requirements against your store and intended channels.

An eesel connection does not replace or configure that native agent. It gives an eesel teammate access to selected Gorgias information and permitted actions. If both systems are present, decide which one handles each workflow and verify that customers do not receive duplicate automated replies.

What to evaluate before connecting another agent

Use a representative ticket rather than a generic demo. For a delivery question, ask whether the agent can find the right ticket, access the current order information, explain the policy, and escalate an exception.

Separate three parts of the setup:

More connected documents do not automatically produce a better answer. Conflicting macros, outdated policies, and unnecessary permissions can make a workflow harder to trust.

Also distinguish helpdesk data from store data. A Gorgias ticket can contain an order reference without providing every live order operation. If you need Shopify lookups, configure that connection and its permissions separately.

Set up Gorgias support through eesel CLI

The eesel CLI operates the same eesel teammate and workspace as the dashboard. A person can use terminal commands, a script can query the setup, and a coding agent such as Claude Code, Cursor, or Codex can read its JSON output.

That is useful when a technical teammate handles the connection while a support manager reviews rules and results in the dashboard. It is not a separate copy of the agent.

1. Inspect the intended teammate

With Node.js 18.17 or newer:

npx @eesel/cli login
npx @eesel/cli whoami
npx @eesel/cli agents

Replace AGENT_ID with the intended teammate’s ID:

npx @eesel/cli integrations --agent AGENT_ID
npx @eesel/cli instructions --agent AGENT_ID
npx @eesel/cli automations --agent AGENT_ID

Review existing enabled automations and permitted actions before adding access. A teammate may already have workflows that can use a new connection.

2. Choose public knowledge or a full connection

The eesel Gorgias guide gives two paths:

• Quick start: read published articles from a public help-center URL. It does not grant tickets, macros, triggers, or actions.
• Full connection: authorize the Gorgias subdomain to add those capabilities.

Start the connection from the CLI:

npx @eesel/cli integrations connect gorgias --agent AGENT_ID

Follow the prompts for your chosen path. For full access, a person opens the approval link and authorizes eesel in Gorgias. The guide notes that an already-signed-in admin may approve the connection without another prompt, so review the intended account before opening it.

A coding agent can hand you that link; the browser authorization remains a human step.

3. Check the selected sources

In the eesel dashboard, Integrations > Gorgias shows Help Center, Macros, and Tickets with source toggles and document counts. From the CLI:

npx @eesel/cli status --agent AGENT_ID

If content needs downloading, run npx @eesel/cli integrations download --help and inspect the available sources before starting the appropriate download. Do not assume that an authorized connection means every source is already ready.

If you upload an approved policy with files upload, it adds knowledge; it does not change standing instructions. Keep those two types of updates distinct.

Source counts and status are operational checks, not an accuracy score. Test whether the teammate uses the relevant macro or policy and knows when information is missing.

4. Start with an internal-note workflow

The Gorgias integration supports leaving an internal note so a human can review and send the proposed reply. Use that action before enabling customer sends.

Decide the ticket scope and permitted actions first. Use the dashboard to create the automation, or ask the teammate to create it with your chosen trigger, ticket filters, and internal-note action. Creating an automation can leave it switched on, so do not treat creation as saving an inactive draft.

Gorgias’s customer-message trigger also covers new tickets; there is no dedicated new-ticket trigger in this eesel integration. It can fire again on later customer replies. Use a clear filter and instructions rather than assuming it runs once per ticket.

Another supported trigger is mentioning @eesel in an internal note for on-demand help. Choose the trigger that fits your review process.

5. Verify the actual ticket

npx @eesel/cli automations --agent AGENT_ID
npx @eesel/cli activity --agent AGENT_ID
npx @eesel/cli approvals --agent AGENT_ID

Open the corresponding ticket in Gorgias. Check that the teammate left a private note rather than a customer reply, used the right policy, and avoided taking an unapproved action.

Also check the existing Gorgias auto-responder. eesel’s guide describes suppressing it on handled tickets, but you should verify the behavior in your setup. That check is not proof that every other native or third-party automation is coordinated.

A held approval is not a completed action. Review the actual result before expanding the workflow.

Let a coding agent assist with inspection

A bounded task could be:

Inspect this eesel teammate’s Gorgias sources, instructions, and automations. Report missing knowledge and any actions that can send customer replies. Ask before changing anything.

JSON output lets the coding agent inspect the setup and follow up on errors. Asking it to seek permission is separate from eesel’s configured action approvals.

CLI chat can invoke actions, so restrict permissions before using chat for tests. For write commands, --dry-run prints the server request without sending it; it does not simulate a ticket or validate answer quality.

For scripts, explicitly select the agent, protect EESEL_API_TOKEN, and verify the intended EESEL_API_URL.

Compare costs without merging the two products

Use Gorgias’s current pricing and your contract to estimate the native helpdesk and AI bill. Check included usage, overages, and how an automated interaction affects helpdesk ticket charges.

eesel’s pricing documentation lists regular support tasks at $0.40 each, billed regardless of outcome. Pay-as-you-go has no platform fee or monthly minimum; annual commitments and Enterprise have separate terms.

An eesel task charge does not replace the Gorgias subscription. Estimate the complete workflow cost and the human review it still needs.

Choose one workflow and verify it

If you want the native Gorgias agent, evaluate its requirements and testing tools. If you want an eesel teammate working in Gorgias, try eesel and inspect its setup through the CLI.

Begin with a narrow internal-note workflow, read the actual notes in Gorgias, and check for competing auto-replies. Expand customer-facing actions only after the results support that decision.