> For the complete documentation index, see [llms.txt](https://docs.eesel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eesel.ai/integrations/overview.md).
# Overview
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.
## 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.
{% hint style="info" %}
**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.
{% endhint %}
## 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.
{% hint style="warning" %}
**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](/automations-and-schedules/automations-and-schedules.md). So you can connect everything you use, test privately in chat, and go live when you're ready.
{% endhint %}
## 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 just ask in chat: tell your teammate what to switch off, gate behind approval, or remove, and it handles it.
{% hint style="warning" %}
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.
{% endhint %}
## 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 tool's API with [Network Access](/apis-and-developer-resources/network-access.md) and a [custom skill](/skills/custom-skills.md) if there isn't.
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 just 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.
Does connecting a tool make my agent start acting in it?
No. Connecting only gives it access. Nothing happens on its own until you turn on a trigger by creating an [automation](/automations-and-schedules/automations-and-schedules.md), so you can connect everything and test privately first.
Which tools can I connect?
Helpdesks (Zendesk, Freshdesk, Intercom, Gorgias, Front, Help Scout, HubSpot, Jira Service Management), live chat (Zendesk Messenger, Fresh Chat, eesel's own chat bubble), team chat (Slack, Microsoft Teams), knowledge (Confluence, Notion, Google Drive, your website, uploaded files), e-commerce (Shopify, Magento), plus Salesforce, Asana and Gmail. Each has its own page in these docs, and anything else with an API works through [Network Access](/apis-and-developer-resources/network-access.md).
## Related
* [Automations and Schedules](/automations-and-schedules/automations-and-schedules.md) to turn triggers on and decide what your teammate does with them
* [Instructions and Memory](/instructions-and-memory/instructions-and-memory.md) to tell it when to use the actions you've enabled
* [Skills](/skills/skills.md) for workflows that run on top of the day-to-day work
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.eesel.ai/integrations/overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.