Channel Settings

The channel settings usually have

In the side menu, open Channels, select a connection in the list, and open the channel settings page.

Open channel settings when you need to check the connection, pause processing, update the webhook, or synchronize data. A Website widget channel has a separate widget settings block here. Channel actions also provide migration to another project. The remaining fields depend on the platform, but the check usually follows the same order: status, token, webhook, synchronization, and error history.

• channel identity card;
• status;
• ID;
• actions;
• token or connection;
• webhook;
• data synchronization;
• special platform settings;
• pause/resume;
• removal;
• channel migration.

Channel actions

Channel actions change the state of an already connected channel. Before pausing, deleting, or migrating it, check whether there are active dialogs and whether the channel is used in agent assignment rules.

• pause;
• resume;
• delete;
• transfer to another project.

Token and validity check

In channel settings, the token card shows whether the token is linked, whether it is valid, when the last check ran, and the validation error text if the platform rejected access.

For Telegram, VK, MAX, and Discord, you can update the token or run a manual check when the action is available for that connection. If the token is invalid, first check whether it was revoked on the platform, then update the token and run the check again.

For VK, the check status belongs to the community token or the connected VK account. If the cabinet shows that the VK token expired or is invalid, refresh VK authorization and then synchronize channel data.

Pause

• the channel stops receiving incoming messages and sending replies;
• channel data and settings are preserved;
• the channel can be activated again on the same page.

Removal

• after confirmation, the channel disappears from the project and no longer receives or sends messages;
• project members have no action in the cabinet for restoring a removed channel;
• before confirming, check the channel name and the workflows connected to it.

Webhook

• the channel webhook lets the platform send events to Senler AI;
• the card shows Active, Setting up or Checking, Not set, and Error states;
• the switch enables or disables event reception;
• when the webhook is disabled, a Set up button is available; when it is enabled, Refresh repeats the setup;
• while the setup is being checked, the card shows progress and remaining time; on failure, it shows the reason returned by the platform;
• if messages do not arrive, webhook is one of the first check points.

Synchronization

In the channel list, open the platform menu for the required channel and select Refresh data. The cabinet compares the channel name, username, avatar, bot ID, and profile URL with the platform when those fields are supported.

The result reports each field separately as updated, unchanged, or failed. A partial error does not roll back successful fields. For example, if the platform returns a new name but the avatar image cannot be downloaded, the name is saved while the previous avatar remains. Fix access or the network error and repeat synchronization. The general background process and its errors also appear in process history.

Channel history

For supported channels, the cabinet can retrieve older messages from the platform. Settings show the loading state, covered period, and the latest error when one occurs.

Loading can be waiting, running, completed, partially completed, unavailable for the platform, or failed. The requested history depth defaults to 30 days and can be changed from 1 to 365 days.

If loading completes partially or fails, some messages may already have been saved. Check the error, channel token, and platform permissions. You can retry during agent auto-training when channel history becomes available for selection.

For an Email channel, also check the incoming email filters: they determine which messages reach the cabinet.