Overview
The Voxloud Trigger node starts an n8n workflow when a specific event occurs in the Voxloud telephony platform. It listens for various call-related events such as incoming calls, call answered, call hangup, outbound call started, click-to-call completion, fax calls, and phone call completions. This node is useful for automating processes based on telephony events, for example:
- Automatically logging call details into a CRM when a call is answered.
- Sending notifications or follow-up emails after a call ends.
- Triggering workflows to handle inbound faxes.
- Initiating post-call surveys or analytics after click-to-call events.
Properties
| Name | Meaning |
|---|---|
| Due to limitations, you can use just one Voxloud trigger for each workflow | Informational notice that only one Voxloud trigger node can be used per workflow. |
| Authentication | Method of authentication; currently supports only "API Key". |
| Event | The Voxloud event type to listen for. Options include: |
| - Call Answered: Triggered when a call is answered | |
| - Call Hangup: Triggered when a call is hung up | |
| - Call Incoming: Triggered when an inbound call is received | |
| - Call Started: Triggered when an outbound or internal call is started | |
| - Click to Call: Triggered after a click-to-call event finishes | |
| - Fax Call: Triggered after a fax event finishes | |
| - Phone Call: Triggered after a phone call event finishes |
Output
The node outputs the webhook payload received from Voxloud as JSON data under the json field. This data contains detailed information about the telephony event that triggered the workflow, such as call metadata, timestamps, caller/callee info, and event-specific details.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Voxloud API.
- Needs proper configuration of the webhook URL in Voxloud via the node’s webhook subscription management.
- Uses Voxloud's REST API endpoints to manage webhook subscriptions (
/webhook-subscriptions).
Troubleshooting
- Webhook registration errors: If the node fails to create or verify the webhook subscription, check that the API key is valid and has sufficient permissions. Also ensure the webhook URL is publicly accessible.
- Multiple triggers limitation: Only one Voxloud trigger node can be active per workflow due to Voxloud API limitations. Attempting to add more may cause conflicts or unexpected behavior.
- Event mismatch: Make sure the selected event matches the expected incoming webhook payload; otherwise, the workflow might not trigger as intended.
- Network issues: Ensure that n8n instance can receive incoming HTTP POST requests at the configured webhook path.
Links and References
- Voxloud API Documentation (for webhook subscription and event details)
- n8n Webhook Node Documentation (general webhook usage in n8n)