> 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/communication.md).

# Communication

Connect Slack, Email or Microsoft Teams so your agent answers your team in the thread from your connected knowledge and does work in your other apps from there.

Your AI teammate answers where your team already asks. It replies in the thread from the knowledge you have connected, and links the source it used. From that same thread it also does work in your other integrations, such as looking things up and drafting replies.

These integrations carry both triggers and actions. Nothing runs until you create an automation. For each action you then choose: run on its own, ask you first, or stay off.

| App                                                                   | What your teammate does there                                                                                                                                                 |
| --------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**Slack**](/integrations/communication/slack.md)                     | Answers in the thread from your knowledge, links the source, and keeps answering follow-ups. It also works your other integrations from that thread.                          |
| [**Gmail**](/integrations/communication/gmail.md)                     | Works one Google mailbox: searches messages, reads threads, drafts or sends replies, and manages labels. Gmail is not self-serve yet, so ask us to turn it on.                |
| [**Email**](/integrations/communication/email.md)                     | Every agent has its own address from day one, nothing to connect. Mail sent to it wakes the agent, and it replies in the thread. It can only write to your workspace members. |
| [**Calendly**](/integrations/communication/calendly.md)               | Reads your Calendly bookings: who a meeting is with, who is hosting, when, and whether it is still on. Read-only, set up with one personal access token.                      |
| [**Microsoft Teams**](/integrations/communication/microsoft-teams.md) | Not available self-serve yet. Contact us to get set up, or use [Slack](/integrations/communication/slack.md) for the same workflow in the meantime.                           |

Not seeing your app? The [integrations overview](/integrations/overview.md) has the full list, and how to ask for one.


---

# 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/communication.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.