Integrations
What an AI agent can actually connect to
A directory with the real status next to every entry. One native calendar connector, one webhook that reaches almost everything else, and a clear line where a connector simply does not exist.
Self-serve today - a dashboard toggle or a documented endpoint does it.
Exists, but hidden until the capability is enabled for your account.
Runs in production; the connection is set up together with the bitpull team.
No native connector. The post-conversation webhook carries the data.
On the roadmap. Not callable today, and this site will not pretend otherwise.
CRM & sales
Get every conversation, lead and callback request into the system your sales team already lives in.
HubSpot
Via webhookNo native app yet. The outbound webhook posts the finished conversation, and a small function or a Zapier/Make step creates the contact, note and task in HubSpot.
Pipedrive
Via webhookPerson, deal and activity are created from the webhook payload. Pipedrive accepts a plain REST call, so no middleware is strictly needed.
Salesforce
Via webhookPost the conversation payload into a Salesforce REST endpoint or a Flow that creates the Lead and Task. Same shape as the HubSpot recipe.
Zoho CRM
Via webhookZoho accepts the webhook through its Functions or through Zapier/Make. Field mapping is the same work as any other CRM.
Custom / in-house CRM
Via webhookThe most direct case: your endpoint receives the JSON and decides what to do with it. Nothing sits in between.
Calendar & scheduling
Let the agent read availability and book appointments while the caller is still on the line.
Calendly
AvailableThe one native calendar connector. Connect over OAuth, pick an event type, and the agent books inside your real availability during the call.
Google Calendar
Assisted setupBooking straight into a Google calendar runs in production, but the connection is set up with the bitpull team rather than by a self-serve OAuth button.
Microsoft Outlook / 365
PlannedNo Microsoft Graph connector today. Two workarounds work now: publish the Outlook calendar into a supported provider, or take the booking as a callback request.
Cal.com
PlannedNot connected today. Cal.com does expose a booking API, so the practical route is the same pattern as any live lookup - see the tools page.
E-commerce
Answer product, order and delivery questions from live shop data instead of a static FAQ.
Shopify
Assisted setupOrder status, delivery and product questions answered from the Shopify Admin API through a declared agent tool. The declaration is self-serve; the execution target is wired with the team.
WooCommerce
Assisted setupSame pattern as Shopify against the WooCommerce REST API, with the WordPress-specific auth and rate-limit caveats that come with it.
Shopware
Assisted setupShopware 6 Store & Admin API can back the same order-status tool. Nothing shop-specific exists in the product yet.
Adobe Commerce / Magento
Assisted setupReachable through its REST API in the same way. Expect more mapping work than Shopify because of the multi-store model.
Channels
Where the conversation happens. One agent and one knowledge base serve all of them.
Website widget
AvailableOne script tag puts voice and text chat on any site. Colours, labels, teasers and mode are set through data attributes.
Phone & SIP
AvailableBuy a number in the dashboard or point your existing trunk at sip.bitpull.ai. Inbound and outbound calls both run through the same agent.
REST API / custom UI
AvailableCreate a session over REST, join the LiveKit room with the returned token, and render whatever interface you want around it.
The same agent and knowledge base answer WhatsApp messages. Set up with the bitpull team, not from the dashboard.
Telegram
Assisted setupAs with WhatsApp: production channel, guided setup, one shared minute pool across channels.
Email summary
AvailableA per-agent address receives the summary of every finished conversation. The lowest-effort way to get conversations out of the platform.
Automation & workflow
The general-purpose bridge: one HTTPS endpoint reaches several hundred downstream tools.
Zapier
Via webhookThere is no bitpull app in the Zapier directory. Catch Hook works today and reaches everything Zapier connects to.
Make (Integromat)
Via webhookA Custom Webhook module receives the payload. Make infers the structure from the first delivery, so send a test first.
n8n
Via webhookSelf-hosted and the most flexible of the three: the raw payload stays in your infrastructure, which matters for call transcripts.
Slack
Via webhookNo native Slack app yet. An incoming webhook plus a small transform turns each finished call into a readable message.
Outbound webhook
Beta · account flagThe mechanism behind most entries on this page. Enabled per account through a capability flag - the Actions tab appears once it is on.
Helpdesk & support
Turn an unresolved conversation into a ticket with the transcript already attached.
Zendesk
Via webhookCreate a ticket from the webhook when the conversation outcome is UNRESOLVED, with the transcript in the first comment.
Freshdesk
Via webhookSame recipe as Zendesk against the Freshdesk tickets endpoint. The outcome field is what decides whether a ticket is worth creating.
Intercom
Via webhookConversations land as a note on the contact. Useful when Intercom is the system of record for the customer, not the channel.
Why so much of this is "via webhook"
Because that is the truth, and because it is less of a compromise than it sounds. bitpull posts a finished conversation - transcript, summary, outcome, sentiment - to one HTTPS URL. Every CRM and helpdesk in the list above has a public API that accepts a record. The distance between those two facts is roughly sixty lines of code, or four steps in Zapier, Make or n8n.
A native connector would save you those sixty lines and cost you the field mapping, the deduplication rule and the escalation logic that are specific to your business anyway. The place where a native connector genuinely wins is during the conversation - availability, order status, customer lookup - and that is what agent tools and the Calendly connector address.
If the system you need is not listed, the question to ask is which of the four patterns it fits: post-conversation data (webhook), live lookup during the conversation (agent tool), a channel to talk on (embedding or telephony), or your own interface (REST API). Almost everything is one of those. support@bitpull.ai reaches the people who can tell you which.
If the answer is "one of those, but we do not want to build it ourselves", that is contract engineering rather than a product question - NEOB, the company behind bitpull, does that work.