Connect an AI receptionist to your CRM: API and webhooks

A receptionist that answers and books is only half the job if the results live in one more dashboard nobody opens. The other half is getting each booking, call and message into the place your business already runs from: a CRM, a job management system, a spreadsheet, a team chat. This guide explains the options in plain terms, so you can talk to a developer, or set up the simple ones yourself.

Four ways to connect

• Webhooks. You give the receptionist a URL, and it posts a message there whenever something happens. Best for “tell my CRM straight away”.
• A REST API. Your system asks for what it needs: calls, bookings, customers, messages, or a new booking to make. Best for a nightly sync, a lookup, or booking from your own website.
• REST hooks. Webhooks you subscribe to through the API, one event at a time, each with its own secret. Best when your system wants to manage its own subscriptions.
• Zapier or a similar tool. Catch a webhook in Zapier and pass it to thousands of apps, with no code.

What usually gets connected

Doing it safely

• Verify every delivery. Check the signature on each webhook against the raw body before you trust it.
• Expect repeats. A delivery that fails is retried, so store each event’s id and skip ones you have seen.
• Keep keys on the server. An API key in a web page or an app can be read by anyone.
• Send only what you need. Call transcripts are personal data in callers’ own words; leave them out unless you need them.

What Ringmere offers today

Ringmere has a REST API and signed webhooks on every plan, Starter included.

• A webhook in Settings, with no code: bookings, reschedules, cancellations, restaurant orders and messages for your team, each signed with HMAC-SHA256, carrying an event id, and retried if your endpoint is down.
• A REST API with keys you make and revoke in Settings, each with scopes: read, write, and call transcripts only when you grant them. It reads calls, bookings, customers and messages, makes bookings with the same checks as a call, and marks messages done.
• REST hooks for events including call.completed, appointment.booked and handoff.created, each with its own signing secret.
• Zapier through Webhooks by Zapier. There is no official Ringmere app in the Zapier directory yet; one is planned.

There are no built-in connectors for particular CRMs such as HubSpot or Salesforce. If yours accepts webhooks or has an API of its own, it can be connected; if it needs a specific integration, tell us which. The API reference has every endpoint, limit, error and event, with signature checks in Node and Python, and the webhooks page shows the no-code setup.

Frequently asked questions