Action (Red block) - a block that specifies the execution of the actions “Start” and “Stop”, “Transaction in AMO CRM”, “Contact in AMO CRM”, “add tags”, “delete tags”, “tag user in chat” , “create email subscriber”, “last chat message not read”, “send email”, “add custom field”.
Can be placed after any other block; adjust its placement according to your intended business logic.
a block of the “action” type has priority over other blocks, and if there are 2 “action” and “message” blocks in parallel, then the action will work first, and then the message
The START and STOP actions allow you to redirect clients from one tunnel to another without subscribing and stop sending messages from the current or any other tunnel. If a user is redirected from one tunnel to another using the START action, the user will not be recorded in the tunnel to which the user will be transferred.
When the user hits this tunnel block, the following actions will be performed: start sending (START) messages starting from a certain block of the selected tunnel AND/OR stopping sending (STOP) messages starting from a certain block of another tunnel.
The action "stoa" is executed 1 time; if, after the action has completed, the sending of a block is initiated, then it will be sent.
"Transaction in AMO CRM"
Transfer a deal from Leeloo to AMO CRM using the "Action" block. Specify 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 transaction is transferred along with the contact
"Contact in AMO CRM"
Using this function, the contact will be transferred from Leeloo to AMO CRM. Also, you must specify the name of the integration. Please note that when transferring a contact from Leeloo to AMO CRM, tag values are transferred automatically.
"add tags" "remove tags"
Now, using the “action” block, you can assign or delete 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 your audience and track what stage of the tunnel a particular user is at.
"tag user in chat"
It works the same way as the same function in the “chat” section.
Specify the user you want to tag and specify the text of the comment.
"create email subscriber"
If your tunnel blocks contain content to be sent by email, when this action is triggered, the content from the tunnel will be sent to the user's mail address. If you specify LGT and email, a “linked account for email” is created and a new tab appears in the client card.
Select the email bot connection. Then specify the tunnel and select LGT. If you do not specify a tunnel, the default tunel will be fixed, but no content will be sent from this tunnel.
"the last message in the chat was not read"
Marks the last message in the chat as unread and the user is accordingly moved to the “unread” tab.
It will only work if there have been previous messages from the user.
"send email"
If the user has an email address specified, then when this function is triggered, the content of the block is sent to the email address.
If you select the “create email subscriber” checkbox, when the block is triggered, a linked email account will be created and content will be sent to email.
"add custom field"
A function that adds a “custom field” to the user when triggered. Click on the “add” button and specify the previously created “custom field”. The information will be recorded in the client card.
"add to sales plan"
When this function is triggered, the user will be added to the sales plan you specified.
Sending an external request
Selecting a request type. Available: POST, PUT, GET
field for placing the URL address where the request will be sent
Account selection point. Information about the specified account will be displayed in the body and query preview
in this paragraph you can specify a description (comment)
button to add variables or subscriber data.
Variables are created in the settings. Read more. Subscriber information You need to select one of the options from the drop-down list. Fallback option: used when user data is not available.
button to check the created request.
Request Headers
Body of the request.
You can specify variables or subscriber data.
Query
Response - will be available after clicking on the "check request" button
Response Mapping
button to add new value
delete value button
button to add a new request header, for the headers section.
