Channels
The Channels page (/channels) lets you connect Nexora agents to the outside world. A channel is a bridge between an external event source — a Telegram message, an incoming webhook, or a cron schedule — and a specific agent in your workspace.

Page Overview
The page opens with a “Channels” heading and the subtitle “Connect agents to Telegram and other external platforms”. A “New Channel” button sits in the top-right corner.
Empty State
When no channels have been created, the page displays:
- A broadcast icon
- “No channels yet” heading
- “Create one to connect an agent to Telegram or other platforms” body text
- A “Create first channel” button that opens the New Channel modal
Channel Types
Nexora supports three channel types, each suited to a different integration pattern.
Webhook
A webhook channel exposes an HTTP endpoint that accepts POST requests. When a request arrives, the payload is forwarded to the assigned agent, which processes it and returns a response.
Common uses:
- Receive GitHub or GitLab push events and trigger a code review agent
- Accept CI/CD pipeline notifications and route them to the Infrastructure Manager
- Integrate with any third-party service that supports outbound webhooks
Schedule
A schedule channel triggers an agent on a cron schedule without any external input. The agent runs at the configured interval, executes its task, and optionally posts results to a connected destination.
Common uses:
- Daily standup summary generated by the Scrum Master agent every morning
- Weekly project status report from the Project Manager agent
- Nightly health check run by the Infrastructure Manager
Schedule channels and the Schedules page (/schedules) are related but distinct. The Schedules page manages cron-based agent triggers globally; a Schedule-type channel is a channel-specific trigger wired to a single agent with optional external delivery.
External Chat
An External Chat channel connects an agent to a real-time messaging platform. Currently supported: Telegram. When a user sends a message to the configured bot, it is routed to the assigned Nexora agent and the response is sent back through the platform.
Common uses:
- Customer support bot that answers product questions via Telegram
- Personal assistant bot that accepts tasks from your phone
- Team notification bot that accepts commands and updates the kanban board
Creating a Channel
Click “New Channel” (top right) or “Create first channel” (empty state) to open the creation modal.

Modal Fields
Title: “New Channel — Connect an agent to an external platform”
| Field | Description |
|---|---|
| Name | Display name for this channel. Example placeholder: Customer support bot |
| Description | Optional — a short note about what this channel does |
| Agent | Dropdown: select the agent that will handle incoming events. Shows all agents in your workspace. |
| Channel type | Radio selector: Webhook | Schedule | External Chat |
| External account | Shown only when External Chat is selected — lets you pick a configured integration (e.g. a Telegram bot token added in Settings → Integrations) |
Action buttons: Cancel · Create
If no external accounts have been configured, the External account field shows: “No external accounts configured yet. Add one in Settings → Integrations.” You must add the integration first before you can create an External Chat channel.
Setting Up a Telegram Channel
This is the most common External Chat configuration. The setup takes three steps.
Step 1 — Add Your Telegram Bot Token
- Open a chat with @BotFather on Telegram
- Send
/newbotand follow the prompts to create a bot - Copy the API token BotFather provides (format:
123456789:ABC-DEF...) - In Nexora, go to Settings → Integrations
- Find the Telegram section and paste your bot token
- Save — Nexora will verify the token with the Telegram API
Step 2 — Create the Channel
- Navigate to Channels (
/channels) - Click “New Channel”
- Enter a name (e.g.
Customer Support Bot) - Select External Chat as the channel type
- Choose your Telegram integration from the External account dropdown
- Select the agent you want to handle messages (e.g. Project Manager or any Assistant agent)
- Click Create
Step 3 — Test the Connection
- Open Telegram and search for your bot by its username
- Send a message
- The agent in Nexora receives the message, processes it, and replies through the bot
Responses from the agent are sent back to the Telegram user in real time. The agent has full access to its configured skills and tools — it can look up project data, run schedules, or call external APIs and return the results to Telegram.
Channel Use Case Reference
The table below maps common real-world scenarios to the appropriate channel type and agent.
| Scenario | Channel type | Suggested agent |
|---|---|---|
| Customer answers product questions via Telegram | External Chat | Any Assistant agent |
| Daily standup posted automatically at 09:00 | Schedule | Scrum Master |
| GitHub push event triggers code review | Webhook | Developer (custom) |
| CI/CD failure notification → platform restart | Webhook | Infrastructure Manager |
| Personal task management from your phone | External Chat | Project Manager |
| Weekly project status summary | Schedule | Project Manager |
| Accept commands from team on Telegram | External Chat | Project Manager |
Managing Existing Channels
Once channels are created, they appear in the channels list. Each card shows:
- Channel name and description
- Channel type badge (Webhook / Schedule / External Chat)
- Assigned agent name
- Status indicator (active / inactive)
- Options to edit or delete the channel
To pause a channel without deleting it, toggle the active state from the channel card or detail view.
Prerequisites Checklist
Before creating your first channel, verify:
- At least one agent exists in your workspace (
/agents) - For External Chat channels: the integration token is added in Settings → Integrations
- For Schedule channels: you know the cron expression for your desired schedule
- For Webhook channels: you have the external service’s outbound webhook URL configuration available
Channels are workspace-scoped. Every agent and integration in your workspace is available for selection when creating a channel.