> 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

Integrations connect your agent to external services, giving it knowledge to read, triggers to listen for, and actions to perform.

**Three components of every integration:**

| Component | Description                                      |
| --------- | ------------------------------------------------ |
| Sources   | Data the agent reads and learns from             |
| Triggers  | Events that activate the agent automatically     |
| Actions   | Things the agent can do in the connected service |

**Key rules:**

* All integration types are available on a paid plan.
* Connecting an integration does NOT auto-activate triggers — you choose what the agent listens for
* All toggles are live — no Save button needed
* Multi-brand support: a single integration (e.g., Zendesk) can connect multiple brands/domains, each configured independently

**Integration page structure (per integration):** Each integration has a settings page with three sections: Sources, Triggers, and Actions. Each item has a toggle and optional configuration link.


---

# 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=<question>&goal=<endgoal>
```

`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.