Five9 logo
Five9
Cloud Contact Center (Enterprise)
Bitrix24 logo
Bitrix24
CRM · Telephony · REST API

Bitrix24 + Five9 Integration

Connect Five9 to Bitrix24 — 5 trigger events, 2 CRM actions, full field mapping and real-time sync. Custom-built, production-grade. Live in 5–10 business days.

Get This Integration → ← All Integrations
5 Triggers
2 Actions
Username/Password + API credentials
API / Webhook
30-day support
Five9 has no native Zapier integration. Integrations use the Five9 REST API + Webhooks directly, or native adapters for Salesforce, ServiceNow, Microsoft Dynamics, Oracle and Zendesk.
Automation Builder — Real Triggers & Actions
Click any event to select
Five9 Triggers
E01
call.created
New call initiated
webhook
E03
call.ended
Call terminated with all metadata
webhook
E04
call.disposition_set
Agent sets call disposition after call
webhook
E05
voicemail.received
New voicemail left
webhook
E08
agent.state_changed
Agent status changes (ready/not ready)
webhook
Bitrix24 Actions
A07
Create Activity
Creates CRM activity (call log, meeting)
action
A01
Create Lead
Creates a CRM lead
action
Field Mapping
Dialer → CRM
contact_phone
Contact.Phone / Lead.Phone
contact_name
Contact.Name / Lead.Name
contact_email
Contact.Email / Lead.Email
call_direction
Activity.Type (Inbound/Outbound)
call_duration
Activity.Duration
disposition
Contact.Lead_Status / Deal.Stage
notes
Activity.Notes / Call.Description
recording_url
Activity.Recording / Custom Field
agent_name
Activity.Owner / Task.Assigned_To
timestamp
Activity.Date / Call.Date
voicemail_url
Activity.Voicemail / Custom Field
campaign_name
Lead.Source / Contact.Campaign
ai_summary
Activity.Notes / Custom Field
Five9 Triggers
E01
webhook
call.created
New call initiated
E03
webhook
call.ended
Call terminated with all metadata
E04
webhook
call.disposition_set
Agent sets call disposition after call
E05
webhook
voicemail.received
New voicemail left
E08
webhook
agent.state_changed
Agent status changes (ready/not ready)
Bitrix24 Triggers
T04
polling
New Activity
New CRM activity created
Five9 Actions
A01
POST /api/contacts
Search or create contacts
A02
POST /api/calls
Initiate call or retrieve data
A03
POST /api/campaigns
Manage campaign lists
A04
POST /api/dispositions
Set or retrieve call dispositions
Bitrix24 Actions
A07
Create Activity
Creates CRM activity (call log, meeting)
A01
Create Lead
Creates a CRM lead
Five9 API
POST
/api/contacts/
Search/create contacts
POST
/api/calls/
Initiate call / get data
POST
/api/campaigns/
Manage campaign lists
GET
/api/recordings/{callId}
Retrieve call recording
Bitrix24 API
POST
/rest/crm.lead.add
Create lead
POST
/rest/crm.activity.add
Log call activity

When an agent sets a call disposition in Five9, the automation maps it to the correct Bitrix24 action:

Disposition CRM Stage / Action Stage
Interested Move deal stage → Qualified SQL / Qualified
Booked / Meeting Set Create calendar event + stage update Meeting Scheduled
Not Interested Update contact status → Disqualified Disqualified
No Answer Re-queue + follow-up task or SMS Attempted (retry)
Voicemail Left Set contact status → Attempted Attempted
Callback Requested Create CRM task → Schedule Callback Callback Scheduled
Wrong Number Flag phone field as invalid Invalid
DNC Requested Set opt-out flag + suppress contact Opted Out
Busy Re-queue with delay timer Re-queue

All fields passed on every Five9 call event — mapped to Bitrix24 fields. Highlighted fields are critical for automation:

callId
sessionId
agentName
ani
dnis
duration
talkTime
holdTime
dispositionName
notes
recordingUrl
queueName
campaignName
contactId
timestamp