Rules of blocks placement. Sending conditions.

• Type of a block "Message"
• Type of a block "First Block"
• Type of a block "Delay"
• Type of a block "Actions"
• Type of a block "Filter"
• Type of a block "Trigger"

There are several types of funnel blocks: First block, Message, Delay, Condition, Action.
A variety of blocks and conditions allows you to implement almost any of your strategies. To ensure your sales funnel works correctly, content sent on time and in full, you need to remember several rules for placing blocks, please see description below.

Type of a Block "Message"

Message (Blue block) – a standard block for a content placement.

It can be installed in any part of the funnel, regardless of types of the neighboring blocks. Upon clicking on this block, the message constructor opens where you can place the desired block content.

Type of a Block "Delay"

Delay (Green block) – a block to create temporary delay, delay with valid parameters and sending a block with content or a block with actions at exactly specified time.

It can be placed after block with content, or after any other block.
Delay conditions:

• Time interval delay- allows setting the relative delay for the block dispatch. As soon as the block is activated, the timer starts for the time interval set in the condition (delay interval). When the timer expires, the message sent to the subscriber.

• Time interval Delay with time frame - activation of the next block after a specified time interval with the indication of valid hours and days of the week for sending it. To choose to send blocks on specific days of the week - click on the "All days" button - after which a list with the name of the days of the week will open - select the ones you need or leave it as it is.

• Send only in time - this field is used if you need to limit the sending of the block by the time of the day. Suppose you do not wish client to receive the block at night. To do this, you must specify the allowed sending time, excluding night time. In "Send only in time" field - specify, for example, from 9:00 to 20:00. You can also select the time zone in which the restriction will apply:

Under this condition, if the block is activated at night, for example at 22:35, then it will not be sent immediately, but will be paused until 9:00. At 9:00 a block will be sent. If the block is activated at the allowed sending time, for example at 12:55, then it will be sent with the set delay.

• Exact sending time- allows you to send a message at the exact time. You can specify Date, Time and Time Zone. If such a block activated before the specified time, then the pipeline will wait for the time to come and only then continue the sending on this branch.

Type of a Block "Action"

Action (Red block) – a block to define the execution of the actions "Start" and "Stop", "Deal in AMO CRM", "Contact in AMO CRM", "add tags", "remove tags", "mark user in chat", "create email subscriber","the last chat message was not read","send email", "add custom field", add sales plan, create sms subscriber, send sms, send external request, FB&Google Analytics

It can be placed after any other blocks, adjust its placement according to your business logic.
The START and STOP actions allow you to redirect clients from one funnel to another without a subscription and stop sending messages from the current or any other funnels. If the user is redirected from one funnel to another by the START action, he will not be fixed in the funnel where the user is transferred.
When a user enters a given block of a funnel, the following actions will be performed: start sending (START) messages beginning from a specific block of the selected funnel AND/OR stop sending (STOP) messages beginning from a specific block of another funnel.
"Lead in AMO CRM "

Transfer a Lead from Leeloo to AMO CRM using the Action block. Indicate the name of the integration, the sales funnel on the AMO CRM side and the funnel stage, also on the AMO CRM side. Please note that the lead is transferred with the contact.
"Contact in AMO CRM "

Using this function, a contact will be transferred from Leeloo to AMO CRM. Also, you should specify the name of the integration.
"Add tags" "Remove tags"

Now, using the "Action" block, you can assign or remove tags to users for whom this block is triggered. First, you need to create a tag, and then specify it in the "select tags" field. Using this function, you can segment the audience and track which stage of the pipeline a particular user is located.
"Notify user in chat"
It works the same way as the same function in the "Chats" section.

Indicate the user you want to tag and specify the comment text.
"Create email account"
If there is a content to send by email in the blocks of your funnel, the content from the funnel will be sent to the user's email address, when this action is triggered. If you specify LGT and email, a "linked account for email" is created in the client's card, a new tab has appeared.

Select an email bot connection. Then specify the funnel and select LGT. If you do not specify a funnel, then default funnel will be committed, however, content from this funnel will not be sent.
"Unread last message"

It marks the last message in the chat as unread and the user accordingly moves to the "unread" tab.
"Send email"
If the user has an email address, the block content is sent to the email address, when this option is triggered.

If you select the check box "create email accounts", a linked email account will be created and the content sent to email, when the block is triggered.

"Add a custom field"
An option that adds the user a "custom field" when triggered.

Click on the "add" button and specify the previously created Custom field". Information will be recorded in the customer's card.
"Add to sales plan" 
The user will be added to the sales plan you specified, when this option is triggered.

"sending an external request"

1. Selecting the type of request. Available: POST, PUT, GET
2. the field for placing the URL where the request will be sent
3. Account selection item. Information about the specified account will be displayed in the body and query previews
4. in this paragraph you can specify a description (comment)
5. button for adding variables or subscriber data. Variables are created in the settings. More details. Subscriber data You need to select one of the options from the drop-down list. Fallback: Used when user data is not available.
6. button to check the created request.
7. Request headers
8. Request body. Can be added Variables or Subscribers data.

1. Query
2. Response - will be available after clicking on the "check request" button
3. Response mapping. it is necessary to place the JSONPath it is also possible to specify the subscriber data from the dropdown list.
4. add new value button
5. delete value button
6. button for adding a new request header for the headers section.

FB&Google analytics

This action allows you to choose an event for FB pixel or for GA integration and it will be sent to a chosen one system when the action block will work in your sales tunnel

Type of block "Filter"

With the help of this block, you can check whether a person matches a certain filter or not.

Match filter - the filter is checked and then the block comes to which the connection will be made.

Does not match the filter - it means that the subscriber does not fall under the filter and can be sent to a separate tunnel branch.


Info: If you edit the "message" block with buttons, you definitely need to edit the "filter" block where you check the pressing of these buttons because. each time after making changes in the "message" block, the buttons receive a new ID


In this block type, you can select any of the filtration panel parameters. For example, in order to track a subscriber clicked on a button or did not click, you need to use the filter "by clicked buttons", and if you need to track whether a person has a tag or not and, depending on this, separate the tunnel branches, use the filter "by tag".

IMPORTANT! It is important to put the "Delay" block between the "Message" and "Filter" blocks, as well as the "Action" and "Filter" blocks, if in the "Message" and "Action" blocks the condition that must be triggered in the "Filter" block is met, which follows the given blocks.

Type of a Block "Trigger"


In this block you can check the conditions of the Site and Order. Inside the block itself, you can configure a delay, after which a separate branch will be sent, to which you will link.

Waiting for - if you make a connection from the "waiting for" output, then as soon as the trigger event you have set is executed, a block will be sent to which the connection will go. For example, if you set the trigger "order completed" and pull the connection from the Waiting for exit, the system will wait for the completion of the order.
Expire at -if during the time you set, the set trigger is not executed, then the connection from the red output of the "trigger" block will work and the trigger will receive the expired status.


Trigger "Order":
Made: This status is basic. As soon as the order is formed, it accepts this status.
As a rule, this status indicates that the client is at the stage of entering payment data.
Complete: if the subscriber has successfully paid for the offer, the order will receive the status "completed"
Failed: if the payment for the order was not successful.


Trigger "Website". This trigger will work when you will add init code of your company to your website code. Init code you can find
URL Equal: will be triggered when visiting the exact link of the site
Domain: this trigger will be triggered when visiting the domain specified in the trigger settings

For it to work the trigger "site", you need to add the init code of your company Leeloo.ai to your site code. you can copy it in the LGT settings like "form", "widget" or "pop-up window" at the step "ready". Copy the init code and place it in the head of your site code. Then add the link to the "trigger" block.

Trigger "webinar room". If you are using integrations with Bizon365 for your webinars, you have an opportunity to set webinar room trigger, which will help you to find out user who have visited your webinars and went specific messages to that one who visited or not your webinar room. This trigger will work after synchronization of your webinar.



As for the "order" trigger, it works without binding to the previous block of the sales tunnel, the main thing is that the trigger block is started in operation. Then, as soon as one of the trigger conditions that you set is met, the subscriber will go further down the branch.


Match with all actions
If it off


If it on



Type of a Block "Note"



Informational block, users will not see it. In this block you have an opportunity to add comments for your teammates who also will work in the sales tunnel, after you.