Telegram and WhatsApp Channel Setup
How the profile-workspace Telegram and WhatsApp controls work, when the workspace is ready for each channel, and what the main channel states mean.
Where you see this in the app
These controls live in Settings → Profile inside the profile-workspace setup area.
The app treats channel setup as part of the profile workspace configuration rather than a separate messaging product.
Telegram setup fields
The visible Telegram controls are:
| Setting | Plain-English meaning |
|---|---|
Telegram bot token | The bot credential for Telegram integration |
Mode | Whether Telegram uses Long Polling or Webhook delivery |
Enabled | Turns Telegram handling on or off |
Auto-reply enabled | Lets the workspace answer automatically |
Webhook secret | Required secret when webhook mode is used |
Webhook path / Webhook URL | Optional overrides for the Telegram webhook endpoint |
The page also tells the user when the workspace is not ready yet: if the profile workspace still needs place + date/time, Telegram setup is not fully ready.
WhatsApp setup fields
The visible WhatsApp controls are:
| Setting | Plain-English meaning |
|---|---|
Enabled | Turns WhatsApp handling on or off |
Auto-reply enabled | Lets the workspace answer automatically |
Process chats | Restricts processing to DMs only or DMs plus groups |
Process senders | Restricts whether only self-chat, only the owner, or any sender can trigger behavior |
Generate QR | Starts the linking flow |
Refresh status | Re-checks the current connection state |
Logout WhatsApp | Disconnects the linked session |
The sender and chat scopes are the main guardrails that keep the automation from listening too broadly.
QR, driver, and connection status
WhatsApp setup also exposes channel-state cues:
| UI signal | What it means |
|---|---|
driver | Whether the app is using mock or real QR-linking mode |
Connection status | Whether the linked session is currently usable |
QR expires | When the current QR code stops being valid |
| mock QR payload warning | A local/testing-only warning that the QR is intentionally non-scannable |
The page explicitly explains that in mock mode the QR is not a real scannable login code. That is expected behavior for local simulation/testing.
What users should check first
If channel setup is not working as expected, the practical order is:
- confirm the profile workspace is active and ready,
- confirm the correct channel is
Enabled, - check whether Telegram mode or WhatsApp driver matches what you intended,
- check connection status or webhook requirements,
- save the channel setup again before assuming the workspace rules are at fault.
This page is the channel-credential and connection layer. The Rules tab is where trigger-driven automation behavior is defined after the channels are ready.
See it in action
Previous
Workspace Rules and Trigger States
How the Rules tab works, what enabled or disabled rules mean, and how schedules, webhook rules, and system triggers are surfaced to end users.
Next
Signed WEBHOOK_EVENT Automation Triggers
How WEBHOOK_EVENT rules are configured, what token and secret fields mean, how signed inbound payloads trigger runs, and how users should troubleshoot rejected webhook events.