"I need to schedule a meeting with someone who knows how to patch the ingress nginx controller vulnerability tomorrow afternoon."
It's a relatively simple request, yet it's one that would typically trigger a flurry of back-and-forth emails describing the actual problem, calendar checks, and manual coordination. But what if instead of all that, you can just call a number and have an agent do it for you? (be warned: i'm going to hit the buzzword quota on this one)
The typical voice assistant experience is a special kind of corporate hell. Press 9 to hear your options again. Press 0 to speak with someone who can't help you. Press any combination of numbers to be reminded that technology hates you personally.
"Sorry, I don't understand that request." Our digital utopia's most common catchphrase.
But here's the interesting part - that utopia isn't a lie anymore. It just took a different form. The new AI voice models are dragging us across the uncanny valley. And on the other side? Something almost human. Something that understands you the first time.
In this guide, I'll show you how I built a voice-powered workflow that does what it promises without all the digital suffering. Just conversation that becomes action. We'll feed it our corporate data. We'll give it tools. We'll create something that doesn't just understand your request - it actually does something about it.
You'll need a few accounts set up:
Don't worry if you're not a developer - we'll focus on configuration rather than coding.

The journey begins where most AI experiences do - with a blank prompt screen and a world of possibility. Eleven Labs provides the canvas, but turning it into something useful requires thoughtful design.
First, I logged into Eleven Labs and created a new assistant (selecting the "Blank template" option). But the real work came in shaping its personality and capabilities.
I wanted an assistant that felt like a helpful colleague rather than a robotic service: "Hi, this is the Mechanical Rock Voice Agent. I can take a message or answer any questions you have. How may I help you today?"
The system prompt however, needs far more attention:
You are the Mechanical Rock virtual receptionist, managing our phone system and helping callers with inquiries about our software development consulting services.
PRIMARY RESPONSIBILITIES:
- Answer questions about Mechanical Rock's software development consulting services
- Take messages when callers wish to leave one
- Assist with booking meetings based on staff availability
WHEN ANSWERING QUESTIONS:
- Provide clear, concise information about our software development services
- If you don't have enough information to answer a specific question, politely explain this limitation
- Maintain a professional, helpful tone throughout the conversation
WHEN TAKING MESSAGES:
- Only request contact details if the caller explicitly wants to leave a message or get in touch
- Collect: full name, company name, and the specific message
- If you already have sufficient context from the conversation, create a concise summary and submit that via the leave-message tool without asking for redundant information
WHEN BOOKING MEETINGS:
1. Use the get-date tool to check current date
2. Use the get-calendar tool to check staff availability
3. Offer the first available 30-minute slot
4. If the suggested time works for the caller, use the book-meeting tool to schedule it
5. If the requested staff member isn't available or there are no suitable slots, suggest leaving a message instead
ERROR HANDLING:
- Never mention technical errors to callers
- if a tool fails, simply say "Looks like I cant confirm for you straight away. I will leave a message for the team to get back to you."
- If any system error occurs, simply say "I'll make sure someone from our team reaches out to you" and proceed accordingly
Always maintain a professional, efficient approach while keeping responses brief and focused on the caller's needs.
This approach created an assistant that didn't just passively take requests but actively helped refine them.
I uploaded embeddings of all of our public information (case studies, offerings, clients, team, etc) to the Knowledge Base, giving the assistant context about what kind of work we do, and who can help out.
For the voice, I had way too much fun exploring them all, but ultimately settled on one that sounded natural but not too expressive - Paul (Australia), with the high-quality setting. It struck the right balance between clarity and warmth, though it did increase response time slightly.
Finally, I set up evaluation criteria to track whether the assistant successfully gathered all required meeting details. This would help me refine the prompts over time based on real conversation data.

Now that your Eleven Labs assistant is set up, we need to configure it to send data to your n8n webhook:
Create a Webhook Integration:
https://your-n8n-instance.com/webhook/4d46109c-9687-448a-803f-39bf593a06fdTest the Integration:

Let's examine the components of our n8n workflow:
When the webhook receives data from Eleven Labs, the first step is to convert this into a format that our AI agent can understand and act upon.
This step is optional, and involves another API call but i've found it far more reliable as this transforms the raw JSON data from Eleven Labs into a clear, actionable prompt for our AI agent. The OpenAI node will parse the voice transcript and any metadata collected by Eleven Labs, identifying key information like requested meeting times or email content.
The AI Agent is the core decision-maker in our workflow:
For our AI Agent to function, it needs a language model:

Now let's connect tools that our AI can use to perform actions:
$fromAI('Start', '', 'string')Now that both your Eleven Labs assistant and n8n workflow are configured, it's time to test the complete system:

Try these examples to test different capabilities of your workflow:
Add Error Trigger nodes to handle cases where:
For production use, implement authentication on your webhook:
Your n8n workflow can be extended to integrate with:
To continuously improve your voice assistant:
Review Conversation History:
Refine Your Assistant's Knowledge:
Optimise Voice Configuration:
To make your assistant available to users:
Look, i know you're all trolls so i turned off the calendar integrations. But still, if you want to see how it works in real life you can ask it some questions about our offerings, previous work, or case studies via that popup in the bottom right.
By combining Eleven Labs' voice technology with n8n's powerful workflow automation and OpenAI's language capabilities, you've created an intelligent voice assistant that can handle real business tasks. This system provides a natural interface for scheduling, messaging, and information retrieval without requiring direct interaction with complex software.
The integration between Eleven Labs and n8n creates a seamless experience where users can speak naturally, have their requests understood, and see those requests fulfilled automatically through the appropriate business systems.
As voice AI continues to evolve, this kind of integration will become increasingly valuable for businesses looking to streamline operations while maintaining a personal touch.
If you'd like to discuss anything related to AI, Workflows, Data, or anything else really - please reach out.
Happy automating!