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 JSON
TriggerAI stepApp actionTransformBranch
11 nodes

Scroll sideways to see all branches

truefalse1. Webhook: Voice Tool CallWebhook01Voice Tool Call2. Map BookingSet02Map Booking3. Calendar: AvailabilityCalendar03Availability4. IF: Slot FreeIF04Slot Free5. Calendar: BookCalendar05Book6. Calendar: Free/BusyCalendar06Free/Busy7. Twilio: SMS ConfirmTwilio07SMS Confirm8. Find Free SlotsCode08Find Free Slots9. Sheets: Call LogSheets09Call Log10. Respond: AlternativesRespond10Alternatives11. Respond: BookedRespond11Booked

Node by node

#NodeTypeWhat it does
01Webhook: Voice Tool CallTriggerPOST /webhook/voice/book-appointment, header-authenticated
02Map BookingTransformSets 8 fields: callId, patientName, phone, service…
03Calendar: AvailabilityApp actionChecks free/busy for the requested window
04IF: Slot FreeBranchTrue if json.available && withinHours is true
05Calendar: BookApp actionCreates the appointment event
06Calendar: Free/BusyApp actionGoogle Calendar free/busy for the next 7 days
07Twilio: SMS ConfirmApp actionSends the confirmation SMS
08Find Free SlotsTransformFinds the two nearest free slots from ALL busy intervals, inside business hours and long enough for the service.
09Sheets: Call LogApp actionAppends a row to the "Bookings" tab
10Respond: AlternativesResponseReturns the JSON response to the caller
11Respond: BookedResponseReturns the JSON response to the caller

How a run goes

  1. The voice agent calls the authenticated webhook with name, service and preferred time.

  2. A Set node maps the request and computes the end time from the service length.

  3. Google Calendar checks availability for that exact window.

  4. IF the slot is free and inside opening hours: create the event, text a confirmation and log the booking.

  5. Otherwise: query free/busy for the next seven days and calculate the two nearest free slots that fit the service length.

  6. 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 nameWhat you need
Voice Agent Shared SecretHeader name and secret value of the remote API
Google Calendar – Front DeskGoogle OAuth client with the Calendar API enabled
Twilio – SMSAccount SID and auth token from the Twilio console
Google Sheets – OpsGoogle OAuth client with the Sheets API enabled

Setup in about 30 minutes

  1. Import the file. In n8n open Workflows, then Import from file, and pick voice-receptionist.json. The workflow arrives inactive.

  2. Create the 4 credentials listed above with exactly those names.

  3. Replace the placeholders with your own IDs:

    • REPLACE_WITH_CALL_LOG_SHEET_ID in “Sheets: Call Log”
  4. 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.
  5. Connect error reporting. Import error-reporter.json once, 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.

  6. 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

100+extra appointments booked monthly
24/7phone coverage
< 2 stool response time, no awkward pauses
1 SMSconfirmation per booking, automatically

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.