The fastest way to learn automation in Bitrix24 (Alaio) is not another theory article — it is a list of working recipes you can rebuild in ten minutes each. Below are 25 of them, grouped by area. Each names the exact building block: a stock feature where one exists, a Market robot where the stock set falls short. Setup basics are in the automation rules guide; everything here drops into the same designer.

CRM data quality

1. Format every phone number on entry. An automation rule on lead or contact creation runs Format phone number: custom prefix, so telephony and messengers always dial a valid number regardless of what the form submitted.

2. Check the fields you depend on are filled. Check if a field is filled gates the process before it runs on an empty email or a missing budget — a wrong-data branch is cheaper than a broken campaign.

3. Fix keyboard-layout typos in names. Fix typos repairs names typed in the wrong layout or with stray characters — the difference between "Malcolm" and "Vfkmrjv" in a greeting line.

4. Search before you create. On a new inquiry, Find contact by phone or email checks whether the person already exists and the workflow updates the found record instead of spawning a duplicate — the mechanics are in the duplicates guide.

5. Pull company data into the deal. Get field value from a related entity copies the industry or payment terms from the linked company, so deal-level reports stop needing manual lookups.

Lead routing and responsibility

6. Round-robin lead distribution. Random employee from list or department assigns each new lead to a random manager from the sales team — at volume the load evens out with zero maintenance; details in the lead distribution guide.

7. Escalate a stuck lead. If a lead sits untouched, Get employee manager resolves the responsible person's supervisor and the workflow notifies them — an SLA with a name attached.

8. Keep responsible in sync everywhere. Change responsible on related moves the deal, its contact and its company to the new owner in one step when territories change.

9. Route by department. Get employee department lets a workflow branch on which unit the responsible belongs to — support tickets to one pipeline, enterprise deals to another.

Deals, conditions and calculations

10. Branch on a single condition. Ternary (if-then-else) returns one of two values depending on a comparison — the compact alternative to duplicating whole branches, covered in the if-then conditions article.

11. Gate on several conditions at once. Compound condition (AND / OR / NOT) evaluates up to several comparisons in one step: budget above threshold AND source is advertising AND country matches.

12. Calculate margin or commission. Percentage of a number computes the percentage right in the workflow and writes it to a field — no exported spreadsheets; more math in the calculations guide.

13. Link the new inquiry to an existing deal. Find deal by condition locates an open deal for the same customer so a repeat request continues the old negotiation instead of starting a parallel one.

14. Write back to the related record. Set field value on a related entity updates the company card when a deal closes — last purchase date, accumulated revenue, status flags.

Dates and timing

15. Measure days since last contact. Difference between two dates turns "last activity" into a number a rule can compare, powering re-engagement triggers; date mechanics live in the dates guide.

16. Compute the next review date. Nearest date by condition picks the closest date matching your rule and stores it, and a native delayed rule fires exactly then.

17. Show a live countdown in the card. The countdown field type displays days remaining to a deadline directly in the deal card — a Market field, not a robot, and managers see the SLA without opening reports.

18. Pause a few seconds between steps. Short pause waits the specified seconds before the next robot runs — enough for an external system or a previous update to settle; see the pause and delay guide.

Tasks

19. Check for an open task before creating one. Find task by condition tells the workflow whether a follow-up already exists, ending the pile of identical "call the client" tasks.

20. Update a task from the process. An update-task robot changes the deadline or responsible on an existing task when the deal moves — task recipes are collected in the tasks automation article.

21. Put the CRM link into the task. A task-to-CRM link robot posts the deal or contact link where the assignee works, cutting the "which client is this about?" round-trip.

Telephony

22. Attach the last call to the record. Find last call by phone number pulls the most recent call — duration, direction, recording reference — into workflow variables; more in the calls guide.

23. Detect the country from the number. Country by phone number resolves the country code so routing, language and pricing rules can branch on geography.

Integrations

24. Query an external API. HTTP request GET/POST calls any REST endpoint and Extract value from JSON by path parses the answer into fields — currency rates, stock levels, delivery status; runs on paid plans.

25. Notify an external system with guaranteed delivery. Reliable webhook retries failed deliveries until your endpoint confirms, which plain outbound webhooks never do — the trade-offs are in the webhooks guide.

Where to go from here

Pick the three examples that map to your loudest daily complaint and build only those — automation earns trust by removing one visible annoyance at a time, not by a hundred-step masterplan. When a scenario needs a brick the designer lacks, check the robot catalog and the field types catalog: if it is missing there too, describe the task to us and it gets built into the shared library.