Integration
Available · All plansaiReceptionist + Webhooks
Get each call’s details and summary delivered to a URL you control, for your own systems to act on.
A webhook is an HTTP request sent to a URL you provide when something happens. With aiReceptionist, the event is a call ending. The call’s details and post-call summary are pushed to your URL, so your own software (a custom CRM, an internal tool, a data warehouse) can store, route or react to them without polling.
How webhooks work with aiReceptionist
Provide an endpoint
Give the receptionist an HTTPS URL your system listens on. Anything that accepts a JSON request works: a serverless function, an internal API, an automation platform’s catch hook.
A call ends
When the conversation finishes, the receptionist assembles the call record: who called, what was captured, and the summary.
The record is delivered
A request carrying that record is sent to your endpoint. Your code decides what to do with it: create a lead, open a ticket, page someone, file it.
Go further when you need to
Real-time use means the receptionist asks your system a question while the caller is still on the line. See the availability block below, or talk to the team about a connection built and maintained for you.
What moves, and when
After the call means a record is pushed once the conversation ends. During the call means the receptionist reads or writes the system while the caller is on the line. Post-call vs real-time, defined.
| What | Direction | When | Status |
|---|---|---|---|
| Caller name and phone number | From the receptionist | After the call | Available · All plans |
| Details captured on the call (your custom fields) The exact fields depend on how your receptionist is configured. | From the receptionist | After the call | Available · All plans |
| Post-call summary | From the receptionist | After the call | Available · All plans |
| Call time and duration | From the receptionist | After the call | Available · All plans |
| A request to your endpoint mid-call, with the answer used in the conversation A workflow node you build and maintain. | Both ways | During the call | Available · All plans |
| Webhook as a channel for reaching the receptionist | To the receptionist | During the call | On the roadmap |
Availability by plan
Read from the same capability matrix as the pricing page.
- Post-call sync
- After a call ends, the summary and details are pushed to the tools you use.
- Available · All plans
- Real-time query: webhook node
- A workflow node that calls your endpoint mid-call and uses the answer.built and maintained by you
- Available · All plans
- Webhook
- Receives and responds to events over HTTP, as a channel in its own right.
- On the roadmap
What you get
- Every call record reaches your own systems automatically
- No polling: your endpoint is called when the call ends
- Works with any stack that can receive an HTTPS request
- The same record Zapier receives, delivered directly to you
Questions
- What format is the payload?
- JSON, sent over HTTPS to the URL you configure. The fields depend on how your receptionist is set up. The caller’s details, captured fields and the post-call summary are the core of it.
- When is the webhook sent?
- After a call ends. The record is assembled once the conversation finishes and then delivered to your endpoint.
- How is a webhook different from Zapier?
- Zapier receives the same call record and maps it into other apps for you. A webhook delivers it to code you control, which suits teams with their own systems or developers.
- Can the receptionist call my API during a call?
- That is a real-time integration. The availability block on this page shows the current status of the self-built webhook node. For a connection built and maintained for you, talk to the team.
Connect Webhooks
Start a free trial and connect it yourself, or talk to sales about a connection built for you.