Bitrix24 Automation Rules and Triggers: Stage-by-Stage Recipes

Bitrix24 automation rules and triggers are two halves of the same CRM engine. An automation rule is an action Bitrix24 performs when a lead or deal enters a stage, such as creating a task, sending an SMS or notifying a manager. A trigger is an event that moves the lead or deal into a stage, such as a form being filled, an email opened, a call made or a payment received. Rules react to stages; triggers change stages.

Once you see that difference clearly, designing a pipeline that follows up on its own becomes much simpler. This guide gives you stage-by-stage recipes for a typical Indian sales pipeline, the exact setup steps, the mistakes we see most often, and how to test before you switch anything on for the whole team.

What is the difference between automation rules and triggers?

Think of each pipeline stage as a room. A trigger is the door that pulls a deal into the room when something happens outside. An automation rule is what happens once the deal is inside the room.

Automation rules (actions):

• Run when a lead or deal enters a stage (immediately, after a delay, or when a condition is met).
• Do work for you: create a task, send an email or SMS, send a WhatsApp template through a connected channel, change a field, assign a responsible person, generate a document, create an invoice, or notify a manager.
• Are set separately for every stage of every pipeline.

Triggers (events):

• Listen for something happening to the client or the deal: a CRM form submitted, an email opened, an incoming or missed call, a message in an Open Channel, a link clicked, an invoice paid, or a field changed.
• Move the lead or deal to the stage where the trigger sits.
• Are also set per stage, so the same event can mean different things in different pipelines.

The common misunderstanding is expecting a trigger to "send a message". It does not. The trigger moves the deal, and the automation rule on the new stage sends the message. Most good Bitrix24 setups are chains: trigger moves the deal, rules on that stage do the work, and the next trigger waits for the client's next action.

Stage-by-stage recipes for an Indian sales pipeline

Below is a pipeline we use as a starting point for many B2B and service businesses in India. Adjust the stage names to your own sales language, but keep the logic of "what moves it in" and "what happens inside".

Two practical notes on this table. First, triggers such as "email opened" depend on the email being sent from inside Bitrix24 with tracking, so emails sent from personal Gmail will not fire it. Second, the WhatsApp and Razorpay steps assume those integrations are already connected to your portal; Bitrix24 does not do them on its own out of the box. If you want ideas beyond these, our list of CRM workflow automation examples has more recipes you can adapt.

How do you set up automation rules and triggers in Bitrix24?

The exact menu wording changes slightly between Bitrix24 versions, but the flow has been stable for a long time. Here is the walkthrough for deals; leads work the same way.

1. Open CRM > Deals and switch to the Kanban view.
2. Select the pipeline you want from the pipeline switcher at the top. Each pipeline has its own automation, so a rule built in "Retail" will not run in "Projects".
3. Click the Automation button (sometimes shown as "Automation rules" or a robot icon). You will see your stages as columns, with a Triggers row and an Automation rules row.
4. Under the stage you want, click Add in the Triggers row and pick the event, for example "Form submitted" or "Invoice paid". Set any filter, such as a specific form name.
5. Under the same or another stage, click Add in the Automation rules row and choose the action, for example "Create task" or "Send SMS".
6. Set who the action is for: the responsible person, a fixed user, or the deal owner's manager.
7. Set when it runs: immediately, after a delay (minutes, hours or days), or at a date taken from a field. You can usually restrict delays to working hours so clients are not messaged at midnight.
8. Add a condition if the rule should run only sometimes, for example "Deal amount above ₹2,00,000" or "Source equals Facebook".
9. Where your version offers it, use the option to apply a rule to all stages (or copy it across stages) for actions that should happen everywhere, such as a stale-deal reminder. Confirm how this behaves in your portal before relying on it.
10. Click Save, then test with a dummy deal before the team starts using it.

Automation rules and triggers are not equally available on every plan. The number of rules, and some advanced actions, vary by Bitrix24 plan, and these limits change over time. Check the current plan comparison on the Bitrix24 website, and read our guide to the Bitrix24 free plan vs paid plans before you design anything complex.

Conditions, delays and the order rules run in

Conditions and delays are where Bitrix24 automation rules and triggers become genuinely powerful, and also where most confusion starts.

Conditions are checked when the rule is about to run, not when the deal entered the stage. If a rule waits two days and then checks "Stage is still Quote sent", it will skip deals that already moved on. That is exactly what you want for follow-ups.

Delays stack in order. Rules on one stage run in the order shown, and a delay on rule two does not hold up rule one. If you want a sequence (Day 1, Day 3, Day 7 messages), build three rules with three different delays rather than one rule with three steps.

Field-based timing is useful for Indian businesses with renewals, AMCs or EMI dates. Put the date in a custom field and set the rule to run "before" or "on" that date.

When the logic needs loops, approvals across departments or many branches, a simple stage rule is not enough. That is the point where Bitrix24 smart processes or business process designer workflows take over.

Common mistakes with Bitrix24 automation

At Acemagick, we audit portals that other teams have set up, and the same problems come up again and again.

Loops between stages. A trigger on Stage B moves the deal there when a field changes, and a rule on Stage B changes that same field. The deal bounces, tasks multiply and nobody knows why. Map every "change field" rule against your "field changed" triggers before saving.

Too many notifications. Every rule that pings a manager feels useful on its own. Fifteen of them together make managers mute Bitrix24 completely. Notify only on exceptions, such as high-value deals, overdue tasks or lost deals, not every stage change.

Rules firing on old deals. When you import historic deals or bulk-move old ones to tidy the Kanban, every rule on the destination stage fires. Clients from last year suddenly get a "Welcome" WhatsApp. Pause or temporarily remove rules before imports and bulk moves, or add a condition such as "Created after" a date.

Triggers that only move forward. By default, triggers are meant to push a deal ahead in the pipeline. Do not design a process that depends on a trigger pulling deals backwards without checking how your portal handles it.

No owner for automation. Rules get added by different people over months. Keep a simple sheet listing each stage, its triggers, its rules and who added them.

How should you test automation before going live?

Testing is the step most teams skip, and it is the one that saves you from embarrassing client messages.

• Use a test pipeline first. Clone your real pipeline's stages into a test pipeline and build rules there.
• Create dummy deals with your own number and email. You will receive exactly what clients would receive.
• Shorten delays while testing. Set "after 3 days" to "after 3 minutes", check the result, then put the real delay back.
• Test each trigger by doing the real action. Fill the actual form, pay a ₹1 test link in your payment gateway's test mode, open the actual email.
• Check the deal timeline. Bitrix24 logs automation activity on the item, which shows which rule ran and when.
• Go live one stage at a time. Switch on the first two stages, watch for a week, then add the rest.

Our step-by-step Bitrix24 CRM implementation process shows where automation testing fits in a full rollout.

Why choose Acemagick as your Bitrix24 Gold Partner

Getting rules and triggers right takes knowledge of both Bitrix24 and your sales process. Here is why Indian businesses choose Acemagick for this work:

• Trusted Bitrix24 Gold Partner based in Chennai, working with businesses across India.
• Automation built in from day one, including Day 1, 3 and 7 automated follow-ups in every implementation.
• Integrations that feed your triggers: WhatsApp Business API with auto replies, software dialer and IVR, Facebook and portal lead sources, and Razorpay payment links.
• Clear first-year pricing (+ GST): ₹30K for 5 users, ₹65K for 50 users, ₹1.2L for 100 users and ₹2.35L for 250 users.
• Training and structure: live Zoom training, recorded videos and an SOP/KRA/KPI framework so the team actually follows the pipeline.
• Support after go-live: on-call support Mon–Fri 10AM–6PM, daily system health monitoring and monthly strategy calls.

If you want your pipeline audited or built from scratch, talk to the Acemagick team and we will map your stages, triggers and rules with you.