How-to
Article MarkdownReport an error

How to configure channels for the Start node?

The Channels trigger runs the section when a user message arrives through a connected channel: Telegram, Viber, WhatsApp, Facebook, Instagram, Widget, Custom channel, etc.

When you need it

  • Bot in a messenger (Telegram, Viber, WhatsApp).
  • Using the widget on the website.
  • Integration with Facebook, Instagram, E-Chat, Zendesk, Email.

What to know

  • Channel — a source of messages (messenger, widget, integration). Each channel requires a separate connection (tokens, webhook, OAuth).
  • Two places to configure — channel connections can be configured both in the Start node and in process (bot) settings. Both options change the same configuration — choose whichever is more convenient.
    • Start node — Node Inspector when the "Channels" trigger is selected: choose channels, enter tokens, connect directly in the scenario editor.
    • Process settings — Process Library → click on bot → "Channels" section (or Settings → Bots → select bot).
  • Connection status — green indicator means the channel is connected; red means enter token or complete OAuth.

Available channels

Messengers

  • Telegram — bot token
  • Viber — token, bot name
  • Facebook — OAuth authorization
  • Instagram — OAuth authorization

Other channels

  • WhatsApp — WhatsApp Business API
  • WhatsApp Maytapi — (if enabled on the instance)
  • Custom Channel — custom webhook
  • Zendesk — Zendesk integration
  • E-Chat — E-Chat integration
  • Mobile Widget — mobile widget
  • Widget — web widget

Integrations

  • eSputnik — email marketing
  • Email — Gmail/Outlook (OAuth or settings-based)

Before you start

Steps

1. Select Channels trigger type

  1. Select the Start node on the canvas.
  2. In Node Inspector, in the Trigger type field, select Channels.

2. Add channels

  1. Click Select channels or Add channel.
  2. In the modal, select the channels you need: Telegram, Viber, WhatsApp, Widget, etc.
  3. Channels are grouped by category: Messengers, Channels, Integrations.

3. Configure connection for each channel

Connection can be configured directly in Node Inspector (right panel) or in process settings — data is synchronized.

In the Start node (Node Inspector):

  • After selecting a channel, a configuration block appears for each channel.
  • Enter the token, complete OAuth, or configure other parameters.
  • Click the connect button — green indicator confirms success.

Telegram, Viber:

Facebook, Instagram:

WhatsApp:

Widget:

Email:

4. Check connection status

  • Green indicator next to the channel name — channel is connected.
  • Red indicator — enter token or complete authorization.

5. Configure launch command (optional)

For Telegram you can use the /start command — it is usually configured in the scenario (node that reacts to text). Detailed channel configuration (webhook URL, commands) is in the bot settings section.

What happens next

The section runs on every user message through the selected channels. If multiple channels are selected, the section reacts to messages from any of them.

How to verify it works

  • Check the green indicator for each channel.
  • Send a test message to the bot in the selected messenger.
  • Verify token validity — expired tokens can cause errors.

Common issues

Problem Solution
Channel not receiving messages Check connection status (green indicator), token validity, messenger webhook settings.
Red indicator Enter token or complete OAuth. Reload the page after connecting.
Facebook/Instagram — won't connect Allow pop-ups for OAuth. Check settings in Facebook Developer.

Start node:

Channel connection (alternative path):

  • Configure bot — channels in process settings
  • Channels hub — index of instructions for each channel (Telegram, Viber, WhatsApp, Widget, etc.)
Using your own AI agent?Install the open skill so your AI agent can work with current official ConnectiveOne documentation.Get the skillNeed support?Couldn’t find the answer or need help from the ConnectiveOne team? Create a request in Client Portal.Create a request