n8n
Connect n8n to trigger automated workflows when events happen in Akol. Works with both n8n Cloud and self-hosted instances.
What It Does
- Triggers workflows — Automatically start n8n workflows when events occur in Akol
- Sends call data — Push call details, summaries, and outcomes to n8n
- Sends appointment data — Notify n8n when appointments are booked
- Sends lead data — Push new lead information to n8n
- Daily summaries — Send daily call statistics to trigger reporting workflows
How to Connect
Create a Webhook Node in n8n
In n8n, create a new workflow with a Webhook trigger node. Copy the webhook URL (production URL).
Open Integrations
Go to Dashboard > Integrations and find n8n.
Add a Webhook
Click Add Webhook, enter a name, paste your n8n webhook URL, and select which events should trigger it.
Click Save
Click Save to activate the webhook.
If you’re using a self-hosted n8n instance, make sure your server is accessible from the internet so Akol can reach it.
Events You Can Send
| Event | When It Fires |
|---|---|
call.started | When a call begins |
call.ended | When a call ends |
appointment.scheduled | When an appointment is booked |
lead.created | When a new lead is captured |
daily.summary | Daily recap of all call activity |
Example Automations
| Trigger | Action in n8n |
|---|---|
| Call ended | Save to Airtable or Google Sheets |
| Appointment scheduled | Send an email confirmation |
| Lead created | Create a HubSpot contact |
| Daily summary | Post stats to Slack |
Security
n8n webhooks use HMAC-SHA256 signatures for verification. The signature is sent in the X-N8n-Signature header along with event metadata in X-Akol-Event and X-Akol-Delivery-Id.
Troubleshooting
n8n Workflow Not Triggering
- Verify the webhook URL is the production URL (not the test URL)
- Make sure your n8n workflow is active
- For self-hosted n8n, check that your server is accessible from the internet
Webhook Delivery Failures
- Akol retries failed deliveries up to 3 times with increasing delays
- Check webhook logs in Dashboard > Integrations > n8n for details
Self-Hosted Connection Issues
- Verify your n8n instance is accessible via HTTPS
- Check firewall rules to ensure Akol’s requests can reach your server
- Verify your SSL certificate is valid
Tips
- Use production URLs — n8n has separate test and production webhook URLs; use the production one
- Send a test event first — Verify your n8n workflow receives data before enabling in production
- Self-hosted advantage — Your data stays on your own server with self-hosted n8n
Last updated on