Channels
A channel receives a message from another tool and routes it to an agent, then carries the reply back. Most channels are set up in the dashboard under Settings › Channels; the rest are set in agentx.json (see the configuration reference).
| Channel | What it does | Where to set it up |
|---|---|---|
| Telegram | Chats with a bot, in private messages or in groups when the bot is tagged | Settings › Channels › Telegram, the setup wizard, or agentx connect telegram. See Connect Telegram |
| Answers from a WhatsApp account that AgentX pairs with by QR code. See Answer customers on WhatsApp | Settings › Channels › WhatsApp, or agentx connect whatsapp | |
| Answers mail sent to a mailbox, in the same thread, over IMAP and SMTP. Each reply waits for your approval unless you turn on auto-send. See Answer customer email | Settings › Channels › Email, or agentx connect email | |
| GitLab | Reacts to issues, merge requests and comments sent by a GitLab webhook | Settings › Channels › GitLab. See Watch GitLab |
| GitHub | Reacts to GitHub webhook events, such as pull requests | Settings › Channels › GitHub |
| Webhooks | Starts workflows from other services (for example Sentry, Stripe, Vercel, or your own) | Settings › Webhooks, or agentx webhook add. agentx webhook sources lists the known sources |
| push | Sends notifications to the AgentX phone app. Outbound only | channels.push, or agentx notifications push |
| ntfy | Sends push notifications to your phone through the ntfy app. Outbound only | channels.ntfy, or agentx notifications ntfy. See Get notified |
| Calls (WebRTC) | Voice calls with an agent in the browser, at /call on the daemon | Settings › Channels › Calls (WebRTC), or channels.webrtc |
Telegram ignores everyone until you allow them. A new Telegram bot drops every message unless the sender is on an allow list: channels.telegram.policy.allowFrom for all bots, or allowFrom on one bot's account. Each entry is a Telegram user ID, a chat ID, or an @username. To run a public bot that answers anyone, such as customers, use the entry "*" on that bot's account: see Let anyone talk to the bot. A dropped message shows in agentx daemon logs as not in allowlist.
WhatsApp also ignores everyone until you allow them. With channels.whatsapp.allowFrom unset or empty, the agent answers no one. List each phone number (with or without +) or chat ID the agent may answer. Once the list has an entry, your own "message yourself" chat on the paired phone is answered too. "*" answers every chat on the account; use it only on a dedicated number. A dropped message shows in agentx daemon logs as not in allowlist. Read Before you pair WhatsApp first; for a customer-facing number, follow Answer customers on WhatsApp.
Keep tagged messages to yourself away from the agent. If a page or script sends messages to your own number, such as sign-in codes, start each one with a fixed tag and list that tag in channels.whatsapp.selfChatSkipPrefixes, for example agentx config set channels.whatsapp.selfChatSkipPrefixes '["[code]"]', then restart the daemon. A message in your "message yourself" chat whose text starts with a listed tag (leading spaces are ignored) is dropped before any run, and is left out of the chat history the agent reads. Each drop shows in agentx daemon logs as self-chat skipped by prefix, with the message id and never its text. Unset or empty: nothing is skipped.
Email also ignores everyone until you allow them. With an account's allowFrom unset or empty, every mail is ignored. agentx connect email sets ["*"], so anyone may write, and each reply still waits for your yes. If the agent's engine can run commands (every engine except sdk), connect prints a warning; pass --allow-from to name who may write. Entries can be addresses or @domain. A dropped mail shows in agentx daemon logs as not in allowFrom, dropped.
Slack and Discord are not supported as live channel adapters in this build. Do not paste their tokens into a stale prompt or example. A connection record alone does not make an adapter run.
Agents can attach files to answers in the phone app and the web chat. The agent saves the file in its workspace and ends its answer with one line per file, <agentx-artifact>{"filename":"charts/orders.png","mime":"image/png"}</agentx-artifact>. The line is removed from the answer. The phone app shows the file under the answer; the daemon's web chat (POST /chat) returns it in artifacts. Agents in the phone app learn this at the start of each conversation.
Keep channel credentials private. The dashboard stores only the name of the environment variable that holds a token; the token itself goes in the .env file next to agentx.json.
Before you pair WhatsApp
Both WhatsApp routes, the WhatsApp channel above and Watch a WhatsApp chat, join your WhatsApp account as a linked device: the same way WhatsApp on a computer joins your phone. Know what that means before you scan the QR code:
- Use a dedicated number. The linked device sees every chat on the account. On a personal number, an agent could answer your family and friends.
- There is a risk of a ban. AgentX talks to WhatsApp through unofficial software, not a WhatsApp product. WhatsApp can restrict or ban a number it thinks is automated. Do not pair a number you cannot afford to lose.
- This is not the WhatsApp Business API. AgentX does not use WhatsApp's official business service, so its rules, templates and verified badges do not apply.
- An unset allow list answers no one. With
channels.whatsapp.allowFromunset or empty, every message is dropped. To list the numbers the agent may answer:- Terminal: in the folder with
agentx.json, run:shPut each allowed number in quotes, separated by commas. A group's chat ID, ending inagentx config set channels.whatsapp.allowFrom '["+15550001111", "+15550002222"]'@g.us, works too. - Terminal: restart the daemon:sh
agentx daemon restart
- Terminal: in the folder with
Check it worked
- Browser: open Settings › Channels. Each channel you set up shows live.
- Terminal: run
agentx channel listto see each channel and the agent it is bound to. - Send a test message on the channel. It appears in Activity, with the agent's reply.
If something is wrong
- A channel shows off or not set up: open it in Settings › Channels and check it is enabled and bound to an agent.
- Telegram stays silent: check the allow list above, then look for
not in allowlistinagentx daemon logs. - Email stays silent: check the account's
allowFrom, then look for[email]lines inagentx daemon logs. Only mail that arrives after the first read is answered. See Answer customer email. - WhatsApp stays silent: check
channels.whatsapp.allowFrom(see Before you pair WhatsApp), then look fornot in allowlistinagentx daemon logs. - A webhook event never arrives: first check that the other tool sent it (its webhook delivery log), then open Settings › Diagnostics in the Hub and Activity.
- Still stuck: run
agentx doctorand follow It's not answering.
