n8n and No-code
You do not need to build a backend to start using Voicetta events.
n8n, Make, and Zapier can receive Voicetta webhooks directly.
For a simple workflow, the setup is:
Voicetta → webhook → automation → your tools
1. Use the production webhook URL
Create the webhook endpoint in:
Settings → Developers
Use the URL provided by your production workflow.
During development, you can use a temporary webhook URL such as webhook.site or an ngrok tunnel.
2. Respond immediately
Your webhook should return 200 as soon as it receives the event.
Do not make your workflow wait for long-running actions before responding.
If the response takes too long, Voicetta will retry the event.
3. Authenticate
You can use a custom header.
For example:
X-Api-Key: your-secretConfigure the same value in your automation platform.
For custom server integrations, HMAC verification is recommended.
4. Keep the timeout at 10 seconds
The default timeout is 10 seconds.
Leave it there unless you have a specific reason to change it.
The important thing is to acknowledge the webhook quickly.
5. Branch on event
If one webhook receives multiple events, branch on:
eventFor example:
call.completed
message.received
message.sent
thread.completedEach event contains the corresponding object:
call
message
threadDeduplicating
Webhook delivery is at-least-once.
The same event can arrive more than once.
Use:
X-Voicetta-Delivery-Idto identify delivery attempts.
Or use:
event_idto identify the underlying conversation record.
Your workflow should be safe to run twice.
Reading data through the API
Use the REST API when you need:
- historical conversations
- data from before the webhook was enabled
- recovery after downtime
- reports
- a specific call, message, or thread
Base URL:
https://api.voicetta.com/v1A minimal workflow
A simple n8n flow can look like:
Voicetta Webhook
↓
Check event
↓
Store conversation
↓
Update CRM
↓
Notify teamOr:
Voicetta Webhook
↓
message.received
↓
Check intent
↓
Create lead / Update CRM / Notify teamVoicetta provides the communication layer.
Your automation decides what happens next.