HubSpot, Pipedrive, Salesforce, Bitrix Guide 2026
An AI voice agent without CRM integration captures half the value. Every call produces data — lead status, qualification score, follow-up needs, calendar booking — that should flow automatically into your sales pipeline. Here's how to wire it for the major CRMs.
Integration Architecture
Standard pattern across all CRMs:
- AI voice agent calls webhook on every call event — call started, in progress, ended, qualified, escalated
- Webhook handler transforms data — maps AI fields to CRM fields
- CRM API write — create or update contact, log activity, schedule task
- Optional: bidirectional sync — CRM updates push back to AI agent (e.g., do-not-call list)
Vapi, Retell, and Bland all support webhooks. The differentiation is how much native integration is built in.
HubSpot Integration
Native integration: Retell AI has native HubSpot connector. Vapi via webhook.
Setup:
- Create HubSpot Private App with
crm.objects.contacts.write+crm.activities.writescopes - Configure webhook URL on AI platform
- Map AI fields to HubSpot properties (call_outcome, qualification_score, callback_requested)
What flows:
- Contact created/updated on first call
- Call activity logged (duration, recording link, summary)
- Deal created if qualified above threshold
- Task scheduled for sales rep follow-up
Time to set up: 4-8 hours.
Pipedrive Integration
Native integration: None of the big platforms have native Pipedrive yet (as of 2026). Webhook-only.
Setup:
- Generate Pipedrive API token (Personal Settings → API)
- Webhook handler maps to
/persons,/deals,/activitiesendpoints - Use Person field "label" for lead temperature (hot/warm/cold)
What flows:
- Person created/found by phone
- Activity logged with call summary
- Deal stage advanced based on qualification
- Note attached with full transcript
Time to set up: 6-10 hours.
Salesforce Integration
Native integration: Vapi and Retell both have first-class Salesforce connectors.
Setup:
- Create Connected App in Salesforce with API access
- OAuth 2.0 flow to AI platform
- Map fields: Lead/Contact creation, Task logging, Opportunity creation
What flows:
- Lead created with all conversation metadata
- Task auto-logged with call recording link
- Opportunity created if conversion criteria met
- Lead Score updated based on AI qualification
Time to set up: 8-16 hours (Salesforce always slower).
Bitrix24 Integration (Common in Georgia)
Native integration: None. Webhook-only.
Setup:
- Create Bitrix24 inbound webhook (Applications → Webhooks)
- AI platform calls Bitrix REST API:
crm.contact.add,crm.deal.add,crm.activity.add - For Georgian Bitrix24 instances, default API is sufficient
What flows:
- Contact created in Bitrix CRM
- Activity (Call) logged with date, duration, summary
- Deal created if qualified
- Optional: WhatsApp/SMS notification via Bitrix bot
Time to set up: 6-12 hours.
Calendar Booking Sync
For appointment-booking agents (clinics, sales calls, hospitality):
- Google Calendar — OAuth + free Google Calendar API. AI books directly. Most common.
- Outlook 365 — OAuth + Microsoft Graph API. Same pattern.
- Calendly — API key + Calendly API. Simpler if business already uses Calendly.
- Cal.com — open-source alternative, free self-hosted.
Best practice: AI checks availability via API before confirming time slot to prevent double-booking.
Common Pitfalls
- Phone number format — CRM expects E.164 (+995…). AI platforms output varies. Normalize before write.
- Duplicate contacts — Always lookup-by-phone first. Create only if no match.
- Time zones — Calendar booking must use customer's timezone, not server timezone.
- Race conditions — Two simultaneous calls to same contact can race. Use phone as natural key.
- Field length limits — Salesforce especially has tight limits. Truncate transcripts before write.