Workflow 05 / Front desk
AI Voice Receptionist Booking
A voice agent answers after-hours calls; n8n books a real calendar slot and texts a confirmation.
- Trigger
- Tool call from a voice agent
- Size
- 11 nodes, 4 credentials
- Typical build
- 10 working days
- Tools
- n8n, Vapi, Google Calendar, Twilio, OpenAI API, Google Sheets
Example scenario: Three-chair dental practice, about 140 missed calls a month
The problem
The practice missed about 140 calls a month during lunch and after 5 pm. Most of them were new patients who booked with a competitor instead of leaving a voicemail.
What the workflow does
The solution
A voice agent (Vapi or Retell) answers the phone and, when the caller wants an appointment, calls an n8n webhook as a tool. n8n checks Google Calendar availability, books the slot, sends an SMS confirmation via Twilio and logs the call. When the slot is taken or outside opening hours, n8n reads every busy interval for the next seven days from the Calendar free/busy API and calculates the two nearest slots that fit the service length and opening hours; the agent offers them in natural speech.
The flow
Drawn from the real JSON
Node names, order and branches are read from the exported file at build time, so this diagram can never drift from what n8n will show you. Dashed lines are connections; amber ones leave an IF, a Switch or an error output.
Download n8n JSONScroll sideways to see all branches
Node by node
| # | Node | Type | What it does |
|---|---|---|---|
| 01 | Webhook: Voice Tool Call | Trigger | POST /webhook/voice/book-appointment, header-authenticated |
| 02 | Map Booking | Transform | Sets 8 fields: callId, patientName, phone, service… |
| 03 | Calendar: Availability | App action | Checks free/busy for the requested window |
| 04 | IF: Slot Free | Branch | True if json.available && withinHours is true |
| 05 | Calendar: Book | App action | Creates the appointment event |
| 06 | Calendar: Free/Busy | App action | Google Calendar free/busy for the next 7 days |
| 07 | Twilio: SMS Confirm | App action | Sends the confirmation SMS |
| 08 | Find Free Slots | Transform | Finds the two nearest free slots from ALL busy intervals, inside business hours and long enough for the service. |
| 09 | Sheets: Call Log | App action | Appends a row to the "Bookings" tab |
| 10 | Respond: Alternatives | Response | Returns the JSON response to the caller |
| 11 | Respond: Booked | Response | Returns the JSON response to the caller |
How a run goes
The voice agent calls the authenticated webhook with name, service and preferred time.
A Set node maps the request and computes the end time from the service length.
Google Calendar checks availability for that exact window.
IF the slot is free and inside opening hours: create the event, text a confirmation and log the booking.
Otherwise: query free/busy for the next seven days and calculate the two nearest free slots that fit the service length.
Respond to Webhook returns a sentence the voice agent reads back to the caller.
Tools and credentials
Credentials are referenced by name inside the JSON. Create each one in n8n under Credentials, using these names, and the nodes connect automatically.
| Credential name | What you need |
|---|---|
| Voice Agent Shared Secret | Header name and secret value of the remote API |
| Google Calendar – Front Desk | Google OAuth client with the Calendar API enabled |
| Twilio – SMS | Account SID and auth token from the Twilio console |
| Google Sheets – Ops | Google OAuth client with the Sheets API enabled |
Setup in about 30 minutes
Import the file. In n8n open Workflows, then Import from file, and pick
voice-receptionist.json. The workflow arrives inactive.Create the 4 credentials listed above with exactly those names.
Replace the placeholders with your own IDs:
REPLACE_WITH_CALL_LOG_SHEET_IDin “Sheets: Call Log”
Adapt it to your business.
- In Vapi (or Retell) add a tool that POSTs name, phone, service and preferred start time to the webhook URL, with the same header token you stored as credential.
- Adjust the appointment length and time zone in the end-time expression of "Map Booking" (cleaning 60 min, everything else 30), and the opening hours both in the withinHours field of "Map Booking" and in the "Find Free Slots" Code node.
- Use a Twilio number that is approved for SMS in your country and put it in the "From" field of the Twilio node.
- Test with a recorded call before you forward your real phone line.
Connect error reporting. Import
error-reporter.jsononce, then open this workflow’s Settings and choose it as the Error workflow. Failed runs are posted to Slack and logged, with a link to retry.Test, then activate. Run the first node with sample data, check each output in the execution view, then switch the workflow to active. Keep the test run for your records.
Example figures for the scenario above, not guarantees
What this kind of build changes
Use it, or have it built for you
The JSON is free to import and adapt. If you would rather have it wired to your own stack and tested on your data, a single flow like this is a fixed-price project.