AI VOICE
RECEPTIONIST

ElevenLabs holds the conversation. The moment the agent needs to do something real, it calls an n8n webhook. n8n does the work, sends the result back, and the talking continues. Neither side could do this alone.

1. PHONE CALL
2. ↓
   ELEVENLABS
3. ↓
   N8N WEBHOOK
4. ↓
   GOOGLE SERVICES
5. ↓
   RESULT
6. ↓
   ELEVENLABS

1. A caller dials the business number. Twilio picks up the connection.
2. ElevenLabs takes the conversation from there. Voice, listening, the works.
3. The agent works out what the caller wants, the way a receptionist would.
4. Need a fact or an action? It fires an n8n webhook tool with the details.
5. n8n runs the operation and hands back structured data. The agent keeps talking, now with the answer.

Four operations. Check, book, move, cancel. All against a real Google Calendar, all inside the call.

CHECK

The agent sends a time range. n8n reads the calendar and works out what is free, honoring business hours, the timezone, existing events, and a minimum gap between bookings.

BOOK

Creates the event with start, end, caller name and email, plus a short summary of what the appointment is about.

MOVE

Takes the event ID and new times, updates the event. Same booking, new slot.

CANCEL

Takes the event ID, deletes the event. Done.

TEMPLATE VALUES / 09:00 TO 17:00, 60 MINUTE MINIMUM GAP, AMERICA/CHICAGO. CONFIG, NOT PRODUCTION RULES. CHANGE THEM.

A Google Sheet plays client database. Thin, but enough for the job.

FIND

Caller says they have been here before and gives an email. The workflow looks it up. Known caller, known history.

ADD

New caller. First name, last name, email, phone, balance. One appended row and they exist now.

After the call, ElevenLabs ships the analysis to n8n. The workflow pulls the caller email, the phone number, and the transcript summary, then appends it all to the Calls sheet. Every conversation leaves a paper trail on its own.

1. CALL
2. ↓
   TRANSCRIPT
3. ↓
   SUMMARY
4. ↓
   N8N
5. ↓
   CALL LOG

FIELD MAP / ELEVENLABS ANALYSIS.TRANSCRIPT_SUMMARY GOES INTO THE CALL SUMMARY COLUMN.

Phone company, voice AI, workflow engine. Each does the part it is good at and stays out of the rest.

1. TWILIO
2. ↓
   ELEVENLABS
3. ↓
   N8N
4. ↓
   CALENDAR / CLIENTS / CALL LOG
5. ↓
   ELEVENLABS
6. ↓
   CALLER

• TWILIO

  The phone number and the inbound connection. Rings, answers, passes it on.

• ELEVENLABS

  The voice, the listening, the instructions, the tool calls. Everything the caller hears.

• N8N

  The hands. Webhooks come in, operations happen, structured results go back.

• GOOGLE CALENDAR

  The schedule. Read and written, never guessed.

• GOOGLE SHEETS

  Client rows and call summaries. The memory that outlives the call.

Five pieces, each doing exactly one job. The repo's setup is six steps and honest about all of them.

ELEVENLABS SETUP

Build the agent: language, greeting, instructions, personality, which LLM, the native end-call tool. Then one custom webhook tool per action. That mapping is the whole integration.

• checkAvailability→AVAILABILITY WEBHOOK
• bookAppointment→BOOKING WEBHOOK
• updateAppointment→UPDATE WEBHOOK
• cancelAppointment→CANCELLATION WEBHOOK
• getClient→LOOKUP WEBHOOK
• addClient→CREATION WEBHOOK

PATTERN, NOT CONTRACT / NAMES SHOW THE SHAPE. YOUR ENDPOINTS, YOUR CALL.

TWILIO SETUP

Get a number, bring it into ElevenLabs, attach it to the agent, set the inbound connection. Four moves.

GOOGLE CALENDAR SETUP

The connected account needs access to the working calendar. Lookup, create, update, delete, all through OAuth. The template ships a demo calendar ID. Replace it with yours or nothing works.

GOOGLE SHEETS SETUP

One spreadsheet, two tabs. Clients holds first name, last name, email, phone, balance. Calls holds email, phone, call summary. Lookup keys off email. Same deal as the calendar: demo ID in, your ID required.

• Import the JSON into n8n, connect Calendar + Sheets OAuth.
• Add ElevenLabs + Twilio credentials, swap in your calendar and sheet IDs.
• Map the n8n webhook URLs into the ElevenLabs tools, test a call.

The model never touches the calendar. It asks for things. n8n does them. That gap is the entire safety story.

• VOICE→understand the caller
• TOOLS→perform actions
• WORKFLOW→enforce logic
• DATA→provide the answer