Creating blocks and their types
The article describes all types of blocks, fields of forms input and shows how to work with them
How to work with blocks
The "Start dialog" block
The "Dialog state" block
The "Primary condition check" block
The "Data transfer" block
The "End of data collection" block
The "Non-state" and "Non-state with condition" blocks
Blocks represent bot responses and the current "state" a client is in. Transitioning to another block (i.e., changing a client’s state) occurs based on specific conditions such as arrows and keywords.
Arrows are transition conditions. In essence, the arrow performs the role of distributor: if the customer chose "Answer 1", he moves to Block 1, if he chooses "Answer 2", he moves to Block 2 and so on.
Read more about arrows in our article Transition conditions
Blocks priority/descending:
Primary condition check
Arrow, Reminder
Start dialogue
Non-State with condition
In this guide, you’ll learn about the different types of blocks, how to create them, and their purpose. To create a block, you need to select the block type in the "Creating a message" menu to the right (the default is "Dialogue state"), in the "Message text" field, type the message that the bot should send to the customer and click "Save".
Let’s take a closer look at each one.
The "Start dialog" block
The "Start dialog" block is a pale green block with a condition. If you enter a keyword or phrase in the "Condition" field, the bot flow will begin from this block when the user sends that specific keyword or phrase. The example below shows a setup where the bot is triggered when the user types "Start".

The "Dialog state" block
The "Dialog state" block is a white block without any conditions. It can only be accessed via an arrow from another block. This block is used for intermediate responses, branching logic, or sending multiple messages sequentially with specific time intervals.

The "Primary condition check" block
The "Primary condition check" block is a bright green block with the highest priority. It can also serve as an entry point to the entire bot flow.
Unlike the "Start dialog" block, conditions in such blocks are evaluated first. If the user enters a matching keyword or phrase during the conversation, the bot will immediately jump to this block — regardless of where the user currently is in the flow.
Example: If a user is chatting with the bot and types "Start", the bot will instantly switch to this block and reply with "Hello!"

The "Data transfer" block
The "Data transfer" block is a yellow block without any conditions. It is used to send data (variable values) to a CRM system, email, or the bot owner’s personal messengers without resetting the data in the builder.
This way, the data remains available for calculations or other actions even after being transmitted.

The "End of data collection" block
The "End of data collection" block is a red block without any conditions. Its main purpose is to form a request.
When the flow reaches this block, all collected user data (variable values) are sent to the CRM system, email, or other social networks as a prepared request.
After the data is transmitted, the variable values are deleted from the builder.

The "Non-state" and "Non-state with condition" blocks
More detailed information about the "Non-state" and "Non-state with a condition" block types is provided in this article.
https://docs.salebot.pro/osnovnye-ponyati.-kaksozda-botovna-salebot.pro/blokine-sostoyanie ссылка
Last updated