Overview

How integrations work in eesel: what your agent reads from each app, what it can do there, how to connect one from chat, and why an automation is what makes it act.

An integration is how your teammate reaches one of your tools. Connect Zendesk and it can read your help center and answer tickets. Connect Confluence and it can answer from your wiki. Connect Shopify and it can look up a real order.

The useful thing to understand is that every integration is built from the same three parts. Once you've set one up, you've effectively learned them all.

For AI agents and scripts

If you are an AI agent setting eesel up on someone's behalf, do not drive the dashboard in a browser. Use one of these instead, in this order:

1. MCP. If your client supports MCP, connect to eesel's MCP server and use its tools to chat, connect integrations and manage automations. See Claude Code and MCP clients.

2. CLI. Otherwise use the eesel CLI. eesel login, eesel integrations connect <platform>, eesel integrations download start, eesel automations. See The eesel CLI and Set up from Claude Code or the terminal.

3. A person for the sign-in. A full connection needs a person to approve it in the tool itself. If the connect command returns a link, print it for them. If it returns a held receipt with no link, ask for one: eesel chat "give me the connect link for <app>". Either way, do not retry it, and check eesel status until the integration shows as connected.

Trigger keys are listed in a Key column on each integration page. Every page states what "connected" and "automation running" look like, so you can check your work.

Sources, triggers and actions

	What it is	Examples
Sources	What your teammate can read. The knowledge it answers from	Help center articles, past tickets, macros, wiki pages, files
Triggers	When your teammate wakes up. The events it can act on	A customer messages, a ticket is opened, someone @mentions it
Actions	What your teammate can do in the tool	Draft a reply, tag a ticket, look up an order, create an issue

Every integration is a mix of these three, and the mix differs. Some are all three: Zendesk gives you knowledge, events to act on, and things to do. Some are sources only, like Confluence, Notion and Google Drive, which your teammate reads but doesn't act in. A few are actions only, where there's nothing to learn but something to do.

Each integration's page in these docs lists exactly what it offers, so you can check before you connect.

Everything pools together. Sources aren't walled off per integration. An agent with Zendesk, Confluence and your website connected searches all of them at once, so a single ticket reply can draw on your help center, your internal wiki and your marketing site together.

Connecting one

The simplest way is to ask. Open your agent's chat and tell it what you use:

"Connect my Zendesk"

It walks you through it, asks for whatever it needs, and confirms when it's done.

Ask, and your teammate pulls up the connection options and walks you through them.

Most integrations offer two ways in:

• A quick start, which reads your public content without a sign-in. Fast, and useful for trying things out

• A full connection, which signs in properly and unlocks past tickets, triggers and actions

You can start with a quick start and upgrade later without losing anything.

If you'd rather click through it yourself, open Integrations in the left sidebar of your dashboard and add it there. Same options either way.

Connecting a tool does not make your teammate start acting. It only gives it access. Nothing happens on its own until you turn on a trigger, which you do by creating an automation. So you can connect everything you use, test privately in chat, and go live when you're ready.

Approvals, on and off

Each integration has its own page in your dashboard listing its sources, triggers and actions, and changes save as you make them. For every action, and for the integration as a whole, you choose how much freedom it gets:

	What it means
Full automation	The action runs on its own, no confirmation needed
Approval only	Your agent prepares the action and waits for you to approve, always allow, or deny it
Off	The action isn't available to your agent at all
Uninstall from agent	Removes the integration from this agent only. The connection stays for your other agents
Uninstall from workspace	Removes the connection entirely, for every agent

To uninstall, click the integration under Integrations in the left sidebar, then the three dots at the top right. Or ask in chat: tell your teammate what to switch off, set to ask you first, or remove, and it handles it.

Uninstalling from the workspace removes the knowledge that came from it, so anything your agents learned from that tool goes with it. If you only want to stop one agent using it, uninstall from that agent instead.

What you can connect

The full integration list lives in your dashboard, under Integrations in the left sidebar. Ask your agent whether you can connect something and it walks you through it: natively if there's an out-of-the-box integration, or through your app's API with Network Access if there is not.

Some integrations need switching on for your workspace before you can use them. If you can't see one you need, ask us in the support chat under Help and support.

FAQ

How do I uninstall an integration?

Click the integration under Integrations in the left sidebar, then the three dots at the top right. Uninstall from agent removes it from that agent only and keeps the connection for your other agents. Uninstall from workspace removes it entirely. Or tell your teammate in chat which one you want.

How do I turn a single action on or off?

Open the integration's page in your dashboard and toggle the action. Each one can run on its own, ask for approval every time, or be off entirely. Changes save as you make them, and you can ask your teammate to change these in chat too.

What happens when I connect?

eesel reads what the tool holds, such as your help center, past tickets, macros or orders, so your agent can answer from it. Nothing changes inside the tool: no automation is turned on, no reply is sent, and whatever you already run there keeps running as before. Your agent only starts acting when you turn on an automation, and any action that changes something asks for your approval first, until you set that action to run on its own.

Which tools can I connect?

Helpdesks (Zendesk, Freshdesk, Intercom, Gorgias, Front, Help Scout, HubSpot, Zoho Desk, Re:amaze, Jira Service Management), live chat (Zendesk Messenger, Fresh Chat, eesel's own chat bubble), team chat (Slack, Microsoft Teams), email (every agent has its own inbox address at @inbox.eesel.ai, so you can forward mail to it), knowledge (Confluence, Notion, Google Drive, Slite, your website, uploaded files), e-commerce (Shopify, Magento, BigCommerce, Stripe, Recharge, AfterShip, QuickBooks), plus Salesforce, Asana, Gmail and Calendly. Most have their own page in these docs, and anything else with an API works through Network Access.

Related

• Automations and Schedules to turn triggers on and decide what your teammate does with them

• Instructions and Memory to tell it when to use the actions you've enabled

• Skills for workflows that run on top of the day-to-day work