UA	US	RU

UA	US	RU

1. Introduction

Definition

"Action" block is the red block in the Sales Funnels builder that performs service operations on the subscriber without sending content to the messenger. It is used at the Engage, Manage, Convert and Retain lifecycle stages. It is the main tool for automating actions on Client's Card, CRM, and communication channels inside the funnel.

The block reads the subscriber's context (tags, fields, communication channels, status in the sales plan) and writes changes back: switches funnels, creates a deal, changes the sales-plan status, adds/removes tags, creates communication channels. It is connected to the "Message", "Filter", and "Delay" blocks and works together with integrations (AMO CRM, Telegram, WhatsApp, FB & Google).

IMPORTANT! The "Action" block has priority over other blocks: if an "Action" and a "Message" block run in parallel, the action will execute first, followed by the message.

B2B operator (marketer, sales manager, or administrator) configures the block: selects an action type from the 21 available, specifies parameters (tag, sales plan, assistant, communication channel, etc.) and connects it to the next block of the funnel.

B2C client (subscriber) does not see the block or its settings — they only experience the results of the actions: receive an SMS/email, are added to the right channel, see their deal in AMO CRM, get access to a Telegram chat, enter a new funnel.

The Client's Card records: added/removed tags, modified custom fields, the fact of creating email/SMS/WhatsApp channels, addition to a sales plan and status changes, the history of starting/stopping AI Assistants, and the fact of switching between funnels.

After reading this you will understand:

what the "Action" block is and the role it plays in the sales funnel;
which 21 action types are available and at which lifecycle stages they are used;
how the block interacts with CRM, the sales plan, tags, and communication channels;
how to configure funnel switching, branch stopping, and AI Assistant launching;
how to pass events to Facebook/Google analytics and manage Telegram chats;
how to create additional communication channels (email, SMS, WhatsApp) for a subscriber;
what limits and priorities to consider when using the block.

Purpose

The "Action" block is the service executor of automations that performs operations on subscriber data and connected systems without sending content. It makes the customer's journey end-to-end: a single funnel orchestrates tags, CRM, the sales plan, communication channels, and integrations. The exact function of the block depends on the lifecycle stage at which it is used.

Engage — "Start"/"Stop" actions move the subscriber between warming funnels and branches, the "Add tags" action segments the audience for further personalization, and "AI assistants (Start)" connects the AI Assistant to warm up new leads in dialogue. The job is to gently engage the subscriber and prepare them for the next step.

Manage — "Notify user in chat" and "Add to unread" return the chat to the manager for manual handling, "Deal/Contact in AMO CRM" and "Add to Sales Plan" move the lead into the sales team's workflow, "Custom fields" update data in the client card. The job is to hand the lead over to a manager with full context and pin responsibility for the result.

Convert — "Create email/SMS account" opens additional channels for follow-up, "Send email/SMS" delivers the CTA through a fallback channel (when the main one is unavailable), "Send external request" connects payments and external services, "FB & Google Analytics" passes conversion events to ad platforms for campaign optimization. The job is to close the deal and capture the conversion in analytics.

Retain — "Change deal Status in Sales Plan" and "Remove from Sales Plan" complete the deal and clear the funnel after the purchase, "Telegram chat/groups" automatically grant the buyer access to a closed Telegram channel or community, "Remove Tags" and "WhatsApp account" actions keep customer-base segments accurate. The job is to retain the buyer, give them product access, and grow LTV.

2. "Action" block configuration overview

Below is each of the 21 action types available in the block. For each action the purpose, configuration parameters, and a screenshot of the dialog are shown. All actions are configured by clicking the block and saved with the "Save" button.

2.1. Start

The START action lets you redirect subscribers from one funnel to another or to a different branch of the current funnel.

When configuring this action you can select only "Delay" and "Message" blocks — these are the block types the START action can route a subscriber to.

2.2. Stop

The STOP action lets you halt the execution of funnel blocks, including an entire connected branch. In the settings you specify a particular block in the target funnel whose execution must be stopped or from which the branch should be stopped.

The "STOP" action does not block message sending — it stops the execution of the planned scenario in the target funnel branch. If the subscriber re-enters the stopped branch, the blocks will be sent again according to the funnel logic.

When configuring this action you can select only "Delay" and "Message" blocks.

For example: stopping a follow-up branch on payment — as soon as the customer purchases on the website, the follow-up message series stops.

2.3. Deal in AMO CRM

To run this action you must have an active integration with AMO CRM. The action creates a deal in AMO CRM. In the settings you specify the sales funnel in which the deal will be created.

2.4. Contact in AMO CRM

The action creates a contact in AMO CRM. To run the block you must have an active integration with AMO CRM. When the contact is created, tag values are passed automatically.

2.5. Add Tags

With the "Add Tag" action you can automatically assign tags to subscribers when they reach the funnel block to which the action is attached. To add a tag you need to create a tag and specify it in the "Select tags" field (1) — or create it directly in the block via the "+ Add" button (2). Tags let you segment the audience and track which stage of the funnel the subscriber is in.

For example: post-purchase, post-registration, or post-quiz tags.

2.6. Remove Tags

The action removes the tag specified in the settings, if the subscriber has it.

2.7. Notify User in Chat

The action behaves the same as "Tag User in Chat" in the "Chats" section. The specified user will be tagged and will receive a notification with a comment on the tag.

For example: notify a manager once the subscriber clicks the "Book" button.

Specify the user you want to tag and the comment text.

2.8. Create Email Account

The action creates the email communication channel in the subscriber's Client's Card, allowing email templates to be sent in the future. When the "Create email account" checkbox is selected, a linked email account is created when the block triggers and the content is sent to the email.

2.9. Add Subscriber to Unread

Marks the last message in the "Chats" section as unread — the subscriber is moved to the "Unread" tab. The action draws managers' attention to the chat with the subscriber.

2.10. Send Email

When this function triggers, the block content is sent to the subscriber's email. The email will be sent only to subscribers who have an active email communication channel. If the subscriber has no email channel, you can create one by ticking the "Create email account" checkbox.

2.11. Add Custom Field

Click the "Add" button and select a previously created custom field. When the subscriber reaches the block to which this action is attached, the value of the selected custom field will be overwritten by the one specified in the block's settings. This information is automatically saved in the Client's Card.

If the custom field does not yet exist — it will be created and added.

2.12. Add to Sales Plan

When this action triggers, a deal will be created for the subscriber in the specified sales plan.

In the block settings, specify: the sales plan (1), the status in which the subscriber is added (2), the manager who will be attached to the deal (3); if no manager is needed — enable the "leave unassigned" checkbox (4); the "no duplication" checkbox (5) prevents creating an identical deal for the same client more than once.

If a manager is selected — the deal is created and assigned to them. If no manager is selected — the distribution defined in the sales-plan settings takes priority.

2.13. Change Deal Status in Sales Plan

When this action triggers, the deal status for the subscriber in the specified sales plan is changed.

IMPORTANT! The action is executed only for subscribers who were previously added to the specified sales plan.

2.14. Remove from Sales Plan

When triggered, the subscriber's deal in the specified sales plan is removed. You can also remove deals across all sales plans — to do that, tick the corresponding checkbox in the block settings.

IMPORTANT! When the action runs, ALL of the subscriber's deals in ALL sales plans are removed.

You can also remove deals in one or several selected sales plans from the list.

2.15. Create SMS Account

When the "Create SMS Account" checkbox is selected, a linked SMS account is created on block trigger and the SMS content is sent. The SMS communication channel will be added to the Client's Card. Once the account is created, the SMS content is sent immediately to the specified phone number.

2.16. Send SMS

If the subscriber has an SMS channel — when this function triggers, the SMS content is sent. You can also create the channel (2) and send the SMS in a single action block (1).

SMS can be used as a fallback channel when the main one is unavailable (e.g., the subscriber has no messenger but does have a phone — the message goes via SMS).

2.17. Send External Request

This functionality lets you flexibly integrate the system with external services, send data, receive and handle responses, and automatically update information in CRM and other systems.

Request type selection. Available methods:

POST — sending data (e.g., creating a deal in CRM);
PUT — updating data (e.g., changing an order status);
GET — retrieving data (e.g., client information).

Field for the URL address where the request will be sent.
Lets you select the account on whose behalf the request will be sent. Information about the selected account is automatically substituted into body and query in the preview.
The ability to add a text description of the request for easier navigation and understanding its purpose.
Button for adding variables or subscriber data. Variables are created in the settings, more details. Subscriber data is selected from a dropdown list. The fallback option is used when user data is unavailable (e.g., no phone number or email in the Client's Card).
Button to check the created request:
- lets you test the request before saving;
- shows the server's response in the Response section.
Request headers — configures the request headers.
Request body — the data passed in the request (available for POST and GET).
Query — parameters added to the URL.
Response — appears after clicking "Check request", contains the server's response.
Response Mapping — configures matching of data from the server response for further use in the system.
Button to add a new value — extends the data being sent.
Button to remove a value — clears unnecessary parameters.
Button to add a new request header for the headers section — configures additional headers for correct API interaction.

2.18. AI assistants

The action lets you manage the AI Assistant's work on the platform inside your sales funnels. AI can play an important role at different funnel stages: improving work efficiency, raising the quality of customer interaction, and speeding up decision-making.

Start — activates the assistant, enabling it to process customer requests in the sales funnel. After starting, the selected AI Assistant will begin receiving incoming messages, analyzing them, and providing responses.

Assistant selection field.
Number of chat messages to pass to the AI Assistant — for analyzing previous messages and understanding context.
Toggle "Include automated messages" — enables or excludes automated messages (smart replies, broadcasts, etc.) from the AI Assistant's context.
Initiated message — when enabled, the AI Assistant sends the first message. The exact message depends on System instructions defined during the Assistant's setup.
System message — text that the AI Assistant reads before responding to the user. For example: "You are a helpful and friendly cooking assistant."

Stop — stops the assistant. After a mass stop, all selected assistants stop interacting with customers.

Restart — resets the current settings and the assistants' communication history. Customer dialogues start anew, as in a fresh session.

2.19. FB & Google Analytics

The action lets you send Facebook (Meta) and Google analytics events at specific stages of the funnel, helping track the effectiveness of user interactions and optimize ad campaigns.

How it works:

When the user reaches a block configured with analytics, an event is automatically sent to the chosen system (Facebook Pixel, Google Analytics, Google Ads).
Events may include conversion information, user actions, transitions, and other parameters.
Data is sent via API.

The analytics block helps automate sending data to ad systems, improving their efficiency and the accuracy of collected information.

2.20. Telegram chat/groups

This functionality lets you automate checking whether a lead is subscribed to a channel or is a member of a group, and also manage their access to Telegram chats directly from Leeloo.AI funnels.

Features:

Check whether a lead is subscribed to a channel or is a member of a group.
Automatic approval of join requests.
Restrict or restore access to groups/chats/channels.

Available block operations:

Check — verifies whether the user is a member of the specified Telegram chat or channel.
Approve — approves the user's request to join the chat (equivalent to Approve Request to Join Chat).
Banned — displays or assigns the "blocked" status to the user in the chat.
Unban — removes the block from the user, allowing them to rejoin.
Remove — removes the user from the chat without blocking them.
Telegram chat — the name of the group/channel.

2.21. Create WhatsApp Account

When the block triggers, a WhatsApp communication channel is automatically created and added to the subscriber's Client's Card. The action links the subscriber's phone number to your WhatsApp communication channel, allowing you to send messages through your personal WhatsApp.

IMPORTANT! If the subscriber does not have WhatsApp or the number is invalid — messages will not be delivered.

Select communication channel — the WhatsApp communication channel connected to the Leeloo.AI platform.

Select tunnel — the sales funnel to which the lead/subscriber is subscribed.

Select LGT — the lead-generation tool to which the lead/subscriber is subscribed within the selected sales funnel.

Select tag — adds a tag to the Client's Card for segmentation or further condition checks and automations.

Related Instructions

Instruction	Purpose

Instruction	Purpose
Туннели	Sales Funnels — overall scenario-building logic and connections between blocks.
Блок «Сообщение»	"Message" block — the blue block that delivers content to the subscriber.
Блок Фильтр	"Filter" block — the gray block that branches subscribers by conditions.
Блок "Инструмент лидогенерации"	LGT block — the entry point for subscribers into the funnel.
Sales Plan	The deal funnel with stages and managers, into which the "Action" block adds the subscriber.
AMO CRM	Integration with an external CRM for creating deals and contacts.
Client's Card	The customer card into which the block writes tags, fields, communication channels, and events.
Теги	Tags — how to create and use tags for subscriber segmentation.

Key Terms

Term	Explanation

Term	Explanation
"Action" block	A red service block in the sales funnel that performs operations on subscriber data and connected systems without sending content to the messenger.
Sales Plan	A deal funnel with stages and manager distribution, into which subscribers can be added via actions.
AMO CRM	An external CRM system with which Leeloo.AI exchanges deals and contacts through the block's actions.
Tag	A subscriber label used for segmentation, which the "Action" block adds or removes.
Communication channel	A way of delivering messages to a subscriber (Telegram, WhatsApp, email, SMS) that the block can create or use to send content.
AI Assistant	An AI helper on the Leeloo.AI platform that can hold a dialogue with a subscriber; started, stopped, or restarted by the "Action" block.
Client's Card	The centralized subscriber profile in Leeloo.AI, where all block actions are recorded: tags, fields, communication channels, deals.
Custom field	A custom subscriber parameter in the client card, the value of which the "Action" block can overwrite.

Action block