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.
Note
AI Coworkers run on NeoGPT, Microsoft Teams, Outlook, Facebook, Jira, Universal Webhook, Google Chat, and Voice, configured from the Coworker’s own Channels tab and drawing on the setup described here.
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 Outlook Mail and Universal Webhook.
Some channels support multiple route types. Each route is configured and credentialed independently.
Prerequisite
Your agent must 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. Manage them under Integrations → Providers.
Configuring Outputs
When an Agentic Flow agent sends a message through a channel, the Output node, with Channel Delivery turned on, controls the format — Adaptive Card templates, HITL approval cards, and placeholder tokens. See Channel Delivery Templates for the full reference.
Available Channels
| Channel | Supported Agents | Route Types | Use Case |
|---|---|---|---|
| Agent Schedule | Agentic Flow, Chatbot | Trigger | Run the agent on a recurring schedule |
| Databricks | Agentic Flow, Chatbot | Trigger | Databricks job or MLflow webhooks trigger the agent |
| Facebook Messenger | Chatbot, Agentic Flow, Coworker | Conversation | Facebook Page messaging and feed events |
| GitHub | Agentic Flow, Chatbot | Trigger | GitHub webhook events trigger the agent |
| Google Chat | Agentic Flow, Coworker | Conversation | Google Chat app in direct messages and spaces |
| Jira | Agentic Flow, Chatbot, Coworker | Trigger | Jira webhook events trigger the agent |
| Microsoft Teams | Agentic Flow, Chatbot, Coworker | Conversation | Teams bot conversations |
| Outlook Calendar | Agentic Flow, Chatbot | Trigger | Calendar event monitoring and meeting triggers |
| Outlook Mail | Agentic Flow, Coworker | Trigger, Conversation, Notification | Email monitoring and automated replies |
| Slack | Chatbot | Conversation | Slack workspace bot |
| Telegram | Chatbot, Agentic Flow | Conversation | Bot-based messaging on Telegram |
| Universal Webhook | Agentic Flow, Coworker | Trigger, Conversation, Notification | Custom webhook integration with any external system |
| Viber | Chatbot | Conversation | Viber Public Account messaging |
| Voice | Coworker | Conversation | Inbound phone calls to a Coworker |
| Chatbot | Conversation | Customer messaging via WhatsApp Business | |
| Zalo | Chatbot | Conversation | Zalo Official Account messaging |
| Zoho Recruit | Agentic Flow | Trigger | Zoho Recruit automation events trigger the agent |