Bitrix24 ↔ SendPulse integration

Leads and deal stages from Bitrix24 land in the right SendPulse mailing lists and start the right automations, and new chatbot subscribers come back to Bitrix24 as leads

Sales work in Bitrix24, mailings and chatbots run in SendPulse. Between them there is usually an export: once a week someone downloads contacts from the CRM, cleans the file and uploads it to a mailing list, and by then half the stages have changed. A client who has already bought still gets the «still thinking?» letter, and a person who wrote to the chatbot never reaches a manager. The Bitrix24 ↔ SendPulse pair keeps the lists in step with the CRM, starts SendPulse automations from deal stages, and turns new chatbot subscribers into Bitrix24 leads. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: Bitrix24 →System page: SendPulse →

What moves between the systems

Bitrix24 → SendPulseA new lead or contact with an email in Bitrix24 is added to the agreed SendPulse mailing list, with name, source and the responsible manager.
Bitrix24 → SendPulseWhen a deal moves to an agreed stage, for example «proposal sent» or «won», Bitrix24 reports it to the pair and the pair sends a matching event to SendPulse, where it starts an Automation 360 sequence.
Bitrix24 → SendPulseA contact whose deal is won or closed as lost is moved between lists, so buyers stop getting «still thinking?» letters and lost clients go to a separate list.
SendPulse → Bitrix24A new subscriber of a SendPulse chatbot is reported to the pair and becomes a lead in Bitrix24 with the channel and the first message, assigned by your distribution rule.
SendPulse → Bitrix24An incoming chatbot message from a person who already has a card in Bitrix24 is written to the timeline of that lead or deal, so the manager sees the conversation next to the deal.

What we connect

We check that your Bitrix24 plan includes access for outside connections: without it the pair cannot read or write CRM data, and we say so before any work.
In Bitrix24 an administrator creates an inbound connection for reading and updating the CRM and an outbound one that reports stage changes; the pair checks the code of every incoming report against the one in its settings.
In SendPulse you create an identifier and a secret for the account; the pair uses them to get temporary access that renews itself every hour.
We agree the map: which stages feed which lists and which events, which chatbots create leads, and how a person is matched (email first, then phone).
We test on a few real deals and a test chatbot subscriber, check the lists and the lead card with you, and only then switch on the whole pipeline.

Automation scenarios

The weekly export

Before once a week a manager exports contacts from Bitrix24, cleans the file and uploads it to SendPulse, and new leads wait for the next export.

After a lead with an email reaches the right list on its own, and nobody handles files.

A buyer gets the «still thinking?» letter

Before the deal is won in Bitrix24, but the follow-up sequence in SendPulse keeps going because nobody told it.

After the won stage moves the contact to the clients list and the follow-up sequence no longer reaches them.

A chatbot subscriber nobody called

Before a person subscribes to the chatbot and asks about delivery, the message stays in SendPulse, and sales never see it.

After a lead appears in Bitrix24 with the first message and a responsible manager.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

Ongoing REST API access in Bitrix24 Cloud is available only on paid plans in the Vibe+ lineup; the entry Essentials plan does not include API access.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25
CRM API methods manage leads, deals, contacts, companies, estimates, invoices and Smart Processes: creating and updating entities, moving them through funnel stages, logging the history in the timeline, generating documents, and launching automation.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25
Bitrix24 supports two kinds of webhooks: an inbound one that calls API methods on behalf of the employee who created it, and an outbound one that sends a Bitrix24 event to an external handler URL.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25
Address books (mailing lists) can be created, edited and deleted through the documented interface, along with other operations on existing lists.
Source: sendpulse.com ↗ checked 2026-09-27
Automation 360 accepts events created and sent from an external system; such an event starts an automation, and created events can be managed afterwards.
Source: sendpulse.com ↗ checked 2026-09-27
Chatbots can send notifications to an external handler whenever subscribers interact with the bot — a new subscription, an incoming or outgoing message, a failed delivery.
Source: sendpulse.com ↗ checked 2026-09-27

Limits

The limits come from both systems. In Bitrix24 Cloud ongoing access for outside connections exists only on some plans, and Bitrix24 limits how fast requests may come, so a large first load of contacts goes in portions rather than all at once. SendPulse access is temporary and renewed every hour, which the pair handles by itself. The pair only moves people who have an email or a chatbot subscription; consent to mailings is your responsibility and stays as recorded in your systems. Letters and sequences themselves are built in SendPulse by your team; the pair decides who gets into which list and when an automation starts.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Will all our old Bitrix24 contacts be added to mailings?

No, only the ones you choose. The first load is a separate pass over a list your team has looked at; after that only new leads and stage changes move.

What if one person has two cards in Bitrix24?

We agree the rule at the start: attach to the card with an open deal, to the most recent one, or put the case on a list for a person. The pair does not merge cards by itself.

Can a deal stage start a chatbot message instead of a letter?

The pair sends the stage as an event to SendPulse Automation 360; which steps that automation contains is set up in SendPulse. We check together which of your channels the automation can use before promising a specific message.