The Deploy tab

The workflow editor has three tabs: Edit, Test and Deploy. The last one answers two questions: which version of the graph is running, and through which channels it can be reached.

Draft versus deployed version

Every save creates a new version of the graph — the “current version”, your draft. Deploying freezes one version number as the deployed one, and every channel serves that snapshot. Until you press the deploy button, edits in the canvas do not change how the live chat, webhook, bot or schedule behave.

The panel header states this in one line:

• Not deployed yet — the workflow exists only as a draft;
• Deployed: version N with a timestamp — what is running right now;
• Current version (X) differs from deployed (Y) — the graph was edited after the deploy;
• You have undeployed changes — either the graph or a channel’s settings moved.

The button at the bottom reads Deploy version N. When there is nothing to publish it is disabled and reads Up to date.

The deployed version can be moved back without touching the draft. The Versions button on the editor toolbar opens the history, where each version offers Load (put its graph into the editor, publishing nothing) and Roll back (make it the deployed one). A rollback changes what is live in production and leaves the current version alone — see validate, save and versions.

The five channels

The left rail lists the channels. Clicking a row opens its settings, the switch next to it turns the channel on, and an amber dot marks a channel whose settings differ from what is deployed.

Public chat

A hosted chat page at a public link of the form /public/chat/<token>, opened without signing in. The link appears after the first deploy. The welcome message is edited here too; it has its own button and saves instantly rather than through a deploy. See public chat.

Widget

An embeddable chat for any website. It is published by its own switch but shares the public token with the hosted page. You configure the accent colour, position (left or right), panel title, launcher text and icon, auto-open and the list of allowed domains; the embed snippet comes in two modes — bubble and inline. Appearance saves instantly with its own button. See widget.

Telegram

Pick a bot from the workspace integrations — without one the deploy is refused. Then configure: which update types you receive (messages are always subscribed, the rest are checkboxes: reactions, inline button taps, member changes, join requests), trigger phrases for groups and channels (* answers everything, empty keeps the bot silent; in private chats it always answers), reply formatting (plain text, MarkdownV2, HTML), native streaming for private chats, running on member events, and answering replies to the bot’s own messages.

A separate block covers group history: the recording of incoming messages that the telegram_history and telegram_search nodes need. Recording is off by default and works as a ring buffer with a per-chat message cap. Next to it sits the bot diagnostics (privacy mode, permissions, last webhook error). See Telegram.

Webhook

Trigger over HTTP: POST to the workflow URL with an Authorization: Bearer <key> header and a {message?, data?} body. The API key is generated on the first deploy of this channel; the panel shows ready-made curl examples, including the one with a session_id in the path that continues an existing conversation. See webhook.

Schedule

The five-field cron expression is assembled by a builder (every N minutes, hourly, daily, weekly, monthly) or typed by hand. The timezone is an IANA name such as Europe/Moscow and defaults to UTC. After a deploy the panel shows the next run time. A missed tick is not replayed — the schedule continues from now. See schedule.

Deploying, step by step

Where to go next