Setting up Bitrix24 CRM Triggers: Sales Automation and Funnels

Deal has been sitting on 'Proposal Sent' stage for a week, the client clicked the link in the email — but the manager doesn't know. Triggers solve this: they move a CRM entity in response to external events, not manager actions. Over 5 years, we've configured triggers for 50+ projects, reducing lead reaction time by an average of 40%. Typical scenario: after sending a commercial proposal, the client ignores the manager but opens the email — the trigger automatically moves the deal to 'Contact Made' stage, and the manager immediately sees the activity.

But not all triggers are equally useful — without proper configuration, they create chaos in the funnel. For example, an 'Incoming Call' trigger without conditions will move a lead to 'Success' stage on the first call, even if the conversation didn't happen. That's why we always design logic with conditions: current stage, responsible person, user field values.

How triggers speed up lead processing

According to Bitrix24 documentation (Triggers of Automation), triggers are implemented via the class \Bitrix\Crm\Automation\Trigger\BaseTrigger. This allows subscribing to any system events: from an incoming call to a webhook from an external service.

Manual labor savings using triggers reach up to 60% at the lead qualification stage. For a company with 500 deals per month, this significantly reduces manual processing costs.

Which triggers are available in Bitrix24

How to set up a trigger in 10 minutes

1. Define the event — choose which external action should trigger the transition: call, email, payment.
2. Create the trigger — go to CRM → [Entity Type] → Robots → Triggers tab. Select the target stage and event type.
3. Configure conditions — limit activation: current stage, responsible person, field values. Without conditions, a trigger will move an entity from any state — this can break business logic.
4. Test — simulate the event and check that the entity moved to the correct stage. For webhooks, use services like Postman.

For a webhook trigger, the system generates a unique URL:

https://portal.bitrix24.ru/rest/WEBHOOK_TOKEN/crm.automation.trigger/?target=DEAL_ID&code=MY_TRIGGER 

This URL is called from the external system — and the deal with ID DEAL_ID moves to the stage linked to the trigger.

Common problem: trigger doesn't fire. Check activation conditions: the trigger may be limited by current stage or field values. Ensure the event actually occurred — for incoming call, check telephony settings; for email, send via CRM. If using a webhook, test with Postman. Note that the email open trigger works only for emails sent from CRM — external mail clients don't support tracking.

What to do if trigger doesn't fire

Typical errors and solutions:

• Email open trigger not working — email was sent directly from mail client, not via CRM. Tracking only works for emails from Bitrix24.
• Webhook trigger not firing — wrong DEAL_ID or code in URL, or webhook token expired (regenerate in REST settings).
• Duplicate transitions — trigger fires multiple times. Add condition 'current stage = X' to prevent re-entering.

What's included in trigger configuration

Our certified specialists with 10+ years experience set up:

• Analysis of current funnel and automation points.
• Designing trigger logic for your business processes.
• Configuring all necessary triggers (up to 5 events per funnel).
• Integration with telephony, email, payment systems.
• Testing and error fixing.
• Documentation and employee training.
• Support for 2 weeks after delivery.

Timelines

• Basic funnel (3-4 triggers): from 2 to 4 hours.
• Funnel with integrations (telephony, webhooks): from 1 to 2 business days.
• Complex automation (multiple funnels): from 3 to 5 business days.

Cost is calculated individually. Contact us for a consultation on your funnel — we will evaluate the project for free. Get a cost estimate today.