Svyazio chatbot builder — visual flow editor with buttons node selected

8 node types. Zero code.

Drag a node onto the canvas, connect it to the next one, fill in a text field. That's the entire workflow. The engine handles the rest.

Start

Entry point of every flow. One per bot.

Message

Send text with variable interpolation. Optional delay before send to feel less robotic.

Buttons

Message plus inline keyboard. Each button has its own outgoing branch. Auto-fallback to numbered text on channels without keyboards.

Input

Collect free text with built-in validation: text, email, phone. Answer saved to a variable.

Condition

Branch on variables or visitor profile fields. AND-logic, top-down evaluation, default branch.

Action

Assign to department or agent, close the session, set variable, or write to visitor profile.

Delay

Pause 0–10 seconds between messages. Makes the bot feel conversational rather than robotic.

Webhook

Call any HTTPS API. Map JSON response fields into session variables. Branch on success or error.

One flow, every channel

Build once. Deploy everywhere.

Our engine is channel-agnostic. A dispatcher renders each node with the native format of every channel — inline keyboards on Telegram and MAX, JSON keyboards on VK, Socket.IO events on the website widget. You never think about it.

On channels without keyboards, buttons auto-fall-back to numbered text. The visitor replies with "1" or "2" and the engine treats it as a click. You write zero fallback code.

Svyazio chatbot builder — input node for collecting email with validation
Svyazio chatbot builder — action node setting visitor profile email
Hand off to humans

Bots qualify. Humans close.

The action node includes assign_department, assign_agent, and close. When the bot finishes qualifying a visitor, it routes the conversation to the right team with all collected variables already visible in the inbox.

Agents see a banner on any conversation with an active bot session and can stop the bot with one click — no matter how complex the flow is.

From idea to live bot in 10 minutes

1

Open the builder

Dashboard → Chatbots → New chatbot. Empty canvas with a Start node.

2

Drag the nodes you need

Message, Buttons, Input, Condition, Action, Delay, or Webhook. Connect them with lines.

3

Fill in text and variables

Use {{variable}} syntax to reference anything the bot collected earlier.

4

Pick when to trigger

On-demand by visitor, on page load, when all operators are offline, or based on keyword/URL match.

5

Publish — live everywhere at once

Your website widget, Telegram bots, VK communities, and MAX channels all start running the new flow immediately. Iterate drafts without breaking production.

Real flows you can copy

The complete guide walks through each one step by step.

SaaS

Lead qualification

Three questions → score the lead → hot leads to Sales, cold to onboarding. Built in ~10 minutes, works on website and Telegram identically.

E-commerce

Order status lookup

Bot asks for order number and email, webhook queries your shop backend, returns tracking info or escalates to support on any error.

After hours

Night bot

Runs only when all operators are offline. Collects email and question, drops a summary into your morning-shift Telegram channel via webhook.

Common questions

Do I need to code?
No. The builder is fully visual. The only node where code-like thinking helps is the webhook, and even there you are pasting a URL and mapping JSON fields.
Does one flow really work on both website and Telegram?
Yes. The engine is channel-agnostic. You build the flow once; the dispatcher translates each node into the right transport for every channel.
Which plan includes chatbots?
Pro plan. It also bundles the AI writing assistant, triggers, departments, analytics, unlimited agents, white-label, and 10 Telegram bots. 7-day free trial, no credit card.
Can I call my own API?
Yes, through the webhook node. HTTPS only, with SSRF-guard against private networks, a 15-second timeout cap, and a 256 KB response limit. Map response fields into variables and branch on success or error.
What if the visitor stops responding?
Sessions time out and the conversation is flagged for agent attention. Nothing gets silently abandoned.
How do agents take over?
Every conversation with an active bot shows a "Stop bot" button. One click ends the session and hands the conversation to the agent with all collected variables.
Can I run multiple flows at once?
Yes. Multiple flows coexist with independent trigger conditions — e.g., a welcome flow on page load, a lead-qualification flow after the visitor opens chat, and a night flow that runs only when operators are offline. The engine picks the highest-priority match; flows never run simultaneously on the same conversation.
Are there analytics on flow performance?
Yes. Per-node analytics show unique sessions reached, funnel drop-off, average session duration, and breakdown by end status (completed / handed off / timed out). Use it to find dead ends and tighten flows.
How do I test before publishing?
Drafts are kept separate from the published version. Edit and iterate on a draft without affecting the live bot. Click Publish when ready — in-flight sessions continue on the version they started on.
Read the complete technical guide

Start building — free for 7 days

Full access to the Pro plan. Every node type. Every channel. No credit card required.

Create free account