Browse step-by-step guides written for non-technical teams. Learn how to build, test, and improve flows with clear examples.
New to FlowCastle? Read these in order. The first guide gets a bot answering you in Telegram in about 10 minutes.
Start with an empty account and finish with a bot that answers you in Telegram: BotFather token, first flow, test run, and publish.
Add one new message to your bot: create a Message block, write the text, connect it with a line, and check it in the Test panel.
A coffee shop welcome message, built step by step: text, the person's name, buttons that lead somewhere, a link button, attachments, AI help, and a test run.
The Starting Step block and every way a conversation can begin: commands, messages, buttons from other flows, deep links, events — and what Deploy does to your Telegram command menu.
A two-question intake bot: turn on Wait for reply, pick a reply type, ask for a phone in one tap, and save every answer into a variable.
Your bot can remember answers and reuse them later: contact, application and system variables, the variable picker, and where the values are stored.
A delivery bot that answers Berlin and everyone else differently: pick what to check, how to compare, connect Yes and No, and test both paths.
Message nodes talk. Action nodes work. Here are the built-in actions you can add to a flow, and what each one is for.
Modules add ready-made actions for outside services: Sheets, Gmail, Stripe, OpenAI and more. Install one, finish its setup, use it like any other action.
The difference between saving and deploying, how the Test panel works, what a deploy actually syncs, and where to look when the bot does not answer.
Payments, AI answers, web chat, notifications and more — open these when you need them.
The Payment block sends a real Telegram invoice from inside a flow. How to price it in Stars or in cards, what each exit means, where the sale is recorded, and what the block will not do.
Set up a plan once and deliver its benefits after each confirmed payment.
One block that talks with your users, answers from documents you upload, and hands the conversation to the right branch — or to a person — when the question is really a task.
Most of what your bot needs to know is already written on your website. Point the importer at the address and it reads the pages for you — no copy-paste, no PDFs.
Write each message once, add translations for the languages you support, and FlowCastle sends every person the right text — automatically.
The texts and picture of your bot's Telegram profile are set in @BotFather, not in FlowCastle. Here is which is which and how to change each one.
Step-by-step: create a web chat bot, copy the embed snippet from the Install tab, and add it to your site as a floating bubble, an inline frame, or a standalone page.
Open-source middleware for a Telegram bot you already run in code. Which package to install, how to get the key, the minimal integration, the handler API, privacy modes and how to check it works.
A bot usually replies to the person it is talking to. Here is how to send something to your team, to a log channel, or to an admin who has to approve it.
A "suggest a post" bot for a channel, a photo contest, a UGC inbox for a brand — people send media, you receive it and decide what to publish. Two ways to build it, from a three-node flow to a moderation group with buttons.
Turn a date question into a calendar people tap: choose the open days, add time buttons, set the time zone, and see what gets saved.
Check every person who asks to join your Telegram channel or group before they get in: an emoji CAPTCHA in a private chat, then approve or decline.
Open the editor next to a guide and follow along on the free plan. No card required.
Start for free