What Otobiz connects to.
Your answers already live somewhere. This is how they reach the customer.
An answer is only as good as the system it came from. These are the systems.
Sign inWhat counts as an integration.
An integration connects Otobiz to another system so data moves between them without anyone copying it by hand. In customer messaging that means three things: the channels customers write on, the store or CRM holding the record an answer depends on, and the automation tools that connect everything else.
Every connection, by category.
What each one actually does once it is on, not what it plugs into.
| Connection | What connecting it does |
|---|---|
Messaging channelsWhere your customers actually write to you. | |
| WhatsApp Business Platform | Connects the WhatsApp Business Account your business owns, so every message lands in the shared inbox and approved templates can be sent when the conversation window has closed. |
| Connects an Instagram professional account so direct messages arrive in the same inbox as every other channel, with no Facebook Page required. | |
| Facebook Messenger | Connects a Facebook Page you administer so Page messages arrive in the shared inbox with the same drafts, approvals, and contact record as every other channel. |
| Telegram | Connects a Telegram bot you create, giving you a live channel in about a minute with no business verification, no template review, and no conversation window. |
| Website chatsoon | Puts a first-party chat widget on your own site so visitors can ask a question without a phone number, with the page and campaign they arrived from known from the first message. |
EcommerceProducts, orders, and the questions they generate. | |
| Product import | Loads your products by hand or from a spreadsheet, so the AI can answer product questions and WhatsApp can show product and catalog messages, without a store connection. |
| Shopifysoon | Keeps products and orders in step with your store, so the AI answers stock, price, and order status questions from live data instead of a spreadsheet somebody maintains. |
| WooCommercesoon | Connects a WordPress store so catalog and order data feed the same conversations, with order events available to trigger follow-up. |
| Magentosoon | Connects an Adobe Commerce store so product and order records ground the answers customers get in chat. |
| Orders pushsoon | Sends order records from your own systems into Otobiz, so a status question is answered from the real order and handed to a person when there is no match. |
CRM and salesKeeping the conversation and the pipeline in step. | |
| Contact import and export | Brings your existing contacts in from a spreadsheet with field mapping, and exports them again, so you are never locked into one tool by your own data. |
| HubSpotsoon | Keeps contacts and conversation activity in step with your CRM, so a salesperson looking at a record sees what was said in chat. |
| Salesforcesoon | Connects leads, contacts, and opportunities so messaging activity appears against the record your sales team already works in. |
| Zoho CRMsoon | Keeps contacts and deal stages in step so conversations and pipeline do not drift apart. |
| LeadSquaredsoon | Connects lead records and stages so messaging follow-up runs against the same pipeline your sales team is working. |
Automation and dataMoving records between tools without writing code. | |
| Outbound webhooks | Tells your own systems the moment something happens in Otobiz, so a message, a campaign result, or a completed sequence reaches them without anything asking. |
| Zapiersoon | Connects Otobiz to thousands of other tools without code, so an event in a conversation can update a record anywhere else you work. |
| Makesoon | Builds multi-step automations between Otobiz and your other systems visually, for cases a single trigger and action do not cover. |
| Pabbly Connectsoon | Wires Otobiz events to other tools without code, as an alternative automation route. |
| Google Sheetssoon | Reads contacts from a sheet and writes conversation outcomes back, which is how most small teams actually keep a shared list. |
Analytics and adsConnecting spend and traffic to the conversations they produced. | |
| Google Analytics | Reads site sessions, engagement, and key events so website traffic and the conversations it produces can be read side by side. |
| Google Search Console | Reads search clicks, impressions, and queries so the demand arriving from search can be compared with the messages it turns into. |
| Meta Adssoon | Connects your ad account so click-to-message campaigns can be created, segments can be pushed as custom audiences, and spend can be read against the conversations it produced. |
| Google Business Profilesoon | Brings your Google reviews into the same inbox as your messages, with a reply drafted from your own tone and information for approval. |
SchedulingAppointments booked in the thread. | |
| Booking page | Publishes your services with real availability so customers book a slot themselves, and the booking creates or links the contact record. |
| Calendlysoon | Connects your existing scheduling tool so a booking made from a conversation appears on the calendar your team already uses. |
PaymentsTaking money without leaving the conversation. | |
| Stripesoon | Sends a payment link inside the conversation and records the result, so a customer can pay without leaving the thread. |
| Razorpaysoon | Sends a payment link in the conversation and records the outcome, which is the usual route for moving cash-on-delivery orders to prepayment. |
| PayUsoon | Sends a payment link inside the conversation and records whether it was paid, so follow-up can branch on the answer. |
Marketing automationSharing audiences and events with the rest of your stack. | |
| Klaviyosoon | Shares audiences and events with your email and lifecycle tooling so a customer is not messaged twice about the same thing on two channels. |
| ActiveCampaignsoon | Connects contacts and automation triggers so messaging is one step in a lifecycle rather than a separate programme. |
| WebEngagesoon | Shares user events and segments with your engagement platform so messaging campaigns fire from the same triggers as everything else. |
| CleverTapsoon | Connects user profiles and events so a messaging campaign can be triggered by the same behaviour that drives your push and in-app messaging. |
| MoEngagesoon | Shares segments and events so messaging sits inside the same lifecycle programme as your other channels. |
Logistics and deliveryShipment status, answered before anyone asks. | |
| Shiprocketsoon | Brings shipment tracking into the conversation so the most common support question is answered from the courier's own data. |
| Delhiverysoon | Connects shipment tracking so delivery questions are answered from the courier record rather than from a guess. |
| ClickPostsoon | Aggregates tracking across couriers so delivery status is answered the same way regardless of who is carrying the parcel. |
DeveloperFor anything a prebuilt connection does not cover. | |
| Public APIsoon | Gives your own systems programmatic access to contacts, conversations, and messages for anything a prebuilt connection does not cover. |
| MCP serversoon | Lets an AI assistant read your conversations and prepare actions through the Model Context Protocol, with the same approvals a person would need. |
| Dialogflowsoon | Connects an existing conversational agent so a business already invested in one can keep it while moving the inbox, approvals, and contact record to Otobiz. |
| Twiliosoon | Adds SMS as a fallback channel for customers who are not reachable on a messaging app. |
Need something that is not here? Name the system and what the connection has to do.
Ask about a connectionCommon questions
How should we judge an integration list?
- Name the two or three systems you genuinely need first, then ask exactly what each connection reads, writes, and keeps in sync.
Can we connect something that is not on this list?
- Tell us what the system is and what the connection needs to do. That second half usually decides how quickly it can be built.
Is there a public API?
- Yes. Endpoints for contacts, conversations, messages, and campaigns, authenticated with keys you create in the workspace, following the same consent and approval rules as the interface.
Can the AI answer order status questions?
- Yes. Connect your store, or push order records in from your own systems, and the answer comes from the real order. When there is no matching order it hands the conversation to a person instead of guessing.
Does connecting a system let it send messages on its own?
- No. A connected system can trigger a message, and that message still passes consent, the reply window, and any approval you have set before it goes.