Stop automation on condition

In Albato you can set up a condition check between steps. The “Stop automation on condition” tool identifies when a certain condition is reached and allows the automation to continue or stop.

Step 1. Adding the tool

In the “Automations” section, open your automation, click the “+” button and select the “Tools” section.



In the list that opens, select the “Stop automation on condition” tool.

Step 2. Configuring the tool

In the window that opens, specify the action that the tool will perform if the specified condition is satisfied. There are two actions available:

Pause automation - if the condition specified in the instrument is met, the linking will stop.

Continue automation - when the condition is met, the automation will continue to work.




Now you need to define the conditions.

To do this, click on the “Add condition” button and fill in the three indicated fields:

Select the broadcast service field for which the tool will check the condition.

Select the type of condition to check.

Specify the value to look up.

Setup for simple condition checking

Let's take a look at setting conditions with an example.

Consider that we will need to configure the tool for the first step “Deal status updated” in the amoCRM service. The task is to verify the information received and select only deals with a certain status.

In the first field, we will select the value “Status (name)”.



In the second field, we will select “Equals” as the condition type.



In the third field we will write the name of the mandatory status of the deal, by which the condition will be checked. In the example, this is the “Sale Completed” status.



At the end, just click “Save” and that’s it! Thus, the automation will continue to work only if the data from the sending service meets the specified condition.

Configuration for checking complex conditions

The condition checking engine also supports the configuration of complex conditions.

Consider a scenario where the trigger should fire when the transaction status is “Sale Completed” or “Customer Exited”. In this case, we can convert the condition to a group of conditions.



Click “Convert to a group of conditions” and configure an additional condition.



Even more flexible customization can be done using a combination of conditions.

Let's say we only need to receive information about large transactions with a budget of more than 1,000 dollars. To do this, just add one more condition to the already existing condition group.

For convenience, we can collapse the first group of conditions using the button in the upper right corner.

When setting up the new condition, we select “Budget” as the check field, set the condition type to “Greater than or equal to” and enter the value in question. It is also important to remember to turn the key to the “AND” position.



At the end, just click “Save” and that’s it!

Now, the link will only be activated for transactions with the status “Sale completed” OR “Customer left”, when the transaction budget is GREATER OR EQUAL to 1,000 dollars.

Cases about using the “Stop automation on condition” tool

Here are some cases that you can solve using this tool.

Case #1

Task: each time the sales manager closes a deal worth more than R$10,000, we send a small souvenir to the customer. The HR department is responsible for sending the souvenir. How can we only notify the head of the HR department about transactions that meet the requirements?

Solution: we will filter the data by the parameters "business status" and "business value". There are features in all CRM systems, but suppose the company uses amoCRM.

We describe the filter in human terms:

If the transaction amount exceeds 10,000 dollars and the transaction moves to “completed” status, we will send a notification with contact details to the head of the HR department.

You must exclude all information that does not matter to the system from the description:

If the transaction amount exceeds 10,000 dollars and the transaction has changed to “completed” status, please send a notification.

Let's formalize the description:

IF (transaction_value > = 100,000 dollars) AND (transaction_status = “completed”) THEN (action - send a notification)

Case # 2

Task: To build end-to-end analytics, you only need to send information about successful and lost transactions to Google Analytics. How to do this?

Solution: we will filter the data by the "transaction status" parameter. Let's continue assuming that amoCRM is used as a CRM.

We describe the filter in human terms:

If the transaction has moved to "successfully completed" or "unsuccessful" status, transfer data about that event to Google Analytics.

Let's formalize the description:

IF (trade_status = "successfully completed") OR (trade_status = "unsuccessful") THEN (action - send an event to the GA)

Case # 3

Task: We have Jivochat installed on our website. Upon completion of each dialog in the CRM system, a task is directed to the responsible operator to contact the user and request feedback on the service. A certain number of users don't leave contact information, only their name, so there's no point in defining a task in these cases. How to delegate tasks in CRM only if user name and phone or email are specified?

Solution: We will filter the data by the parameters "username", "mailbox" and "phone number". We can omit the CRM system used.

We describe the filter in human terms:

If the user has indicated his name and telephone number, or postal address, then we pass the task on to the responsible operator.

Let's formalize the description: IF (username <> “”) AND (phone_number <> “” OR email <> “”) THEN (action is to define a task)

Updated on: 04/05/2023