# Triggers & Channels

> Start agent runs from webhooks, A2A calls, email, Slack, Microsoft Teams, Telegram, and Jira

Run your agents where your team already works. An agent can answer messages in Slack, Microsoft Teams, Telegram, and Jira issues. It can also reply to email, and run when your code sends it a request. It keeps the same tools, skills, and [Guardrails](https://archestra.ai/docs/agents/guardrails) everywhere.

| Where | How the Agent Is Chosen |
| --- | --- |
| [Slack](https://archestra.ai/docs/agents/triggers-and-channels/slack), [Microsoft Teams](https://archestra.ai/docs/agents/triggers-and-channels/ms-teams), [Telegram](https://archestra.ai/docs/agents/triggers-and-channels/telegram) | You assign an agent to each channel or direct message. |
| [Jira](https://archestra.ai/docs/agents/triggers-and-channels/jira) | Each Jira bot is pinned to one agent, with project bindings and project instructions. |
| [Incoming Email](https://archestra.ai/docs/agents/triggers-and-channels/email) | Each agent gets its own email address. |
| [Webhook (A2A)](https://archestra.ai/docs/agents/triggers-and-channels/webhook-a2a) | Each agent gets its own endpoint. |

<span id="assigning-channels"></span>

## Add a Channel to an Agent

A channel is one place where people message the agent: a Slack or Microsoft Teams channel, a Telegram group, or a direct message. The agent you add it to answers the messages sent to the bot there.

![An agent's Messaging Channels tab with Slack, Teams, and Telegram channels and an email address](https://archestra.ai/docs/automated_screenshots/agents-triggers-and-channels_agent-channels.webp)

1. Connect the provider first. Each provider's page shows how.
2. Open the agent's **Messaging Channels** tab and click **Add channel**.
3. To change the channel's instructions or reply behavior, click **Settings** on it.

To see every channel at once, open the provider under messaging channel settings. Microsoft Teams and Telegram list each channel with its agent, whether it replies to all messages, and its settings. Personal chats stay hidden until you show them.

For Jira, [connect the bot and projects](https://archestra.ai/docs/agents/triggers-and-channels/jira#connect-jira) in messaging channel settings. Its agent stays pinned to that Jira identity.

## Conversation History

The agent remembers the conversation, so a follow-up such as "and for last month?" works without repeating the details.

- **In a thread:** in a Slack thread, a Microsoft Teams channel thread, or a Telegram topic, the agent reads the whole thread. Start a new thread for a new topic.
- **In a chat without threads:** in a Teams direct message or group chat, or a Telegram chat, Archestra keeps the history. To start a new conversation, send `reset` as the whole message. `new chat`, `new conversation`, and `start over` also work.

What to know:

- After 8 hours with no messages, the next message starts a new conversation. The reply says so.
- A long conversation is summarized, and the bot says so.
- In a group chat, the reply footer names the person who started the conversation (everyone in the chat shares its history). Each message still runs with the sender's own permissions.

## Explore

- [Webhook (A2A)](https://archestra.ai/docs/agents/triggers-and-channels/webhook-a2a.md): Call an agent over HTTP with the A2A protocol
- [Incoming Email](https://archestra.ai/docs/agents/triggers-and-channels/email.md): Give each agent an email address that runs the agent and replies in the thread
- [Slack](https://archestra.ai/docs/agents/triggers-and-channels/slack.md): Give each Archestra agent its own Slack bot
- [MS Teams](https://archestra.ai/docs/agents/triggers-and-channels/ms-teams.md): Connect Archestra agents to Microsoft Teams channels
- [Telegram](https://archestra.ai/docs/agents/triggers-and-channels/telegram.md): Connect Archestra agents to Telegram chats and groups
- [Jira](https://archestra.ai/docs/agents/triggers-and-channels/jira.md): Connect a Jira service account to an Archestra agent and answer issue comments
