Your AI Connector Docs

Connecting a Tool We Do Not List

“Do you integrate with X?” is the most common integration question we get, and for most tools the honest answer is: not natively, but you can connect it, and here is the shortest route.

What Is Built In

These are the only integrations with a dedicated screen in the app:

Everything else (CRMs like Zoho, Pipedrive, Salesforce or Flowlu, phone systems, clinic and practice management software, spreadsheets, and in-house tools) connects through one of the four general routes below. There is no waiting list to get onto: they work today.

The Four Routes

1. Send data out with webhooks

The platform fires an event to a URL you choose whenever something happens: a new contact, an incoming or outgoing message, a booked appointment, a tag added, a deal moving stage, and more. Point that at your CRM (directly, or through Zapier, Make or n8n) and your other system stays in sync without you writing a poller.

Start here: Webhooks.

2. Bring data in with the API

Anything you can do in the app you can do from your own code or from an automation tool: create contacts, add tags, send messages, read conversations, create appointments. Zapier, Make and n8n all talk to it with nothing more than your API key.

Start here: API Access.

3. Let the AI call your system live, mid-conversation

If you need the AI to look something up while it is talking to a customer, such as stock levels, an order status or a patient’s next available slot, that is a Custom Function or an MCP server. The AI decides when to call it and uses the answer in its reply.

4. Bring the whole channel in yourself

If the thing you want to connect is a messaging channel we do not support, a custom channel lets your system hand us incoming messages and take our replies back out for delivery.

What About a Tool With No API?

Some systems, clinic and practice management software especially, have closed or partner-only APIs. Nothing can integrate with those directly, including us. The workarounds that actually hold up:

  • Meet in the middle. If both systems can talk to a spreadsheet, a shared inbox, or an automation tool like Zapier, Make or n8n, use that as the bridge.
  • Ask the vendor for API access. Many “closed” APIs are open on request, or on a higher plan.
  • Keep the two jobs separate. Let the platform own the conversation and the booking, and let the other system own its records. A webhook that notifies your team is often enough; full two-way sync is usually not what the business actually needed.

Before You Build

If you are planning something substantial, email support with what you are trying to connect and in which direction. We can usually tell you within a day which of the four routes fits and whether the events you need already exist.

Next Steps