Channels
Channels connect a published OneByZero Neo agent to external platforms — messaging apps, enterprise tools, automation triggers, and custom webhooks. Once a channel is configured and enabled, the agent begins handling messages or events from that platform without any additional integration work.
Route Types
Every channel connects through one or more routes. The route type determines the direction of communication:
Conversation — Bidirectional. The external platform sends a message, the agent processes it and replies back. Used for messaging channels (WhatsApp, Slack, Teams, etc.).
Trigger — Inbound only. An external event fires the agent; no reply is sent back through that channel. Used for webhook and schedule-based channels (GitHub, Jira, Agent Schedule, etc.).
Notification — Outbound only. The agent sends a message proactively to the external platform. No inbound trigger. Used alongside conversation routes in Teams and Outlook Mail.
Some channels support multiple route types. Each route is configured and credentialed independently.
Prerequisite — Channel Gateway MCP
All channels that use Conversation or Notification routes require the Channel Gateway MCP to be enabled at two levels before the channel can send or receive messages:
Global level — Admin Panel → MCP Servers → Channel Gateway → Enable and Deploy
Workspace level — Workspace Settings → MCP → Channel Gateway → toggle ON
Trigger-only channels (GitHub, Jira, Databricks, Zoho Recruit, Outlook Calendar, Agent Schedule) do not require Channel Gateway MCP.
Your agent must also be published before a channel can be attached to it.
How to Add a Channel
Open an agent in the Builder and navigate to the Channels tab.
Click Add Channel and select the channel from the dropdown.
Select the route type (Conversation, Trigger, or Notification — depending on the channel).
Enter the required credentials and configuration settings.
Click Create Channel. Ensure the channel toggle is set to Enabled.
Credentials entered here are stored at workspace level and can be reused across agents.
Available Channels
Channel |
Supported Agents |
Route Types |
Use Case |
|---|---|---|---|
Agentic Flow, Chatbot |
Trigger |
Run the agent on a recurring schedule |
|
Agentic Flow, Chatbot |
Trigger |
Databricks job or MLflow webhooks trigger the agent |
|
Chatbot, Agentic Flow |
Conversation |
Facebook Page messaging and feed events |
|
Agentic Flow, Chatbot |
Trigger |
GitHub webhook events trigger the agent |
|
Agentic Flow, Chatbot |
Trigger |
Jira webhook events trigger the agent |
|
Agentic Flow, Chatbot |
Conversation, Notification |
Teams bot and proactive channel notifications |
|
Agentic Flow, Chatbot |
Trigger |
Calendar event monitoring and meeting triggers |
|
Agentic Flow |
Trigger, Conversation, Notification |
Email monitoring and automated replies |
|
Chatbot |
Conversation |
Slack workspace bot |
|
Chatbot |
Conversation |
Bot-based messaging on Telegram |
|
Agentic Flow |
Trigger, Conversation, Notification |
Custom webhook integration with any external system |
|
Chatbot |
Conversation |
Viber Public Account messaging |
|
Chatbot |
Conversation |
Customer messaging via WhatsApp Business |
|
Chatbot |
Conversation |
Zalo Official Account messaging |
|
Agentic Flow |
Trigger |
Zoho Recruit automation events trigger the agent |