Overview
The Voicenter Trigger node listens for incoming webhook events from the Voicenter telephony platform. It enables workflows to react to different types of call-related events by receiving data pushed from Voicenter. Common use cases include identifying callers, logging detailed call records, or routing calls based on caller profiles.
Practical examples:
- When a user calls your number, the node receives the caller ID and checks if it matches a client in your system.
- Receiving detailed Call Detail Records (CDR) for every call to analyze call duration, status, and other metrics.
- Implementing custom IVR (Interactive Voice Response) routing logic by identifying callers and directing calls accordingly.
Properties
| Name | Meaning |
|---|---|
| Path | The URL path segment where the webhook listens for incoming requests. For example, setting this to "voicenter" means the webhook URL will include /voicenter/{type}. |
| Trigger Type | The type of event to listen for. Options: • PopUp Screen: Triggered when a user is calling; sends caller ID to check client association. • CDR Notifications: Receives detailed information about every call. • External IVR: Identifies incoming calls by phone number to enable custom routing scenarios. |
| Respond | Defines when and how the node responds to the webhook request. Options: • When last node finishes: Returns data after the last executed node completes. • Using 'Respond to Webhook' node: Response is handled explicitly by a dedicated node in the workflow. |
Output
The node outputs JSON data representing the webhook payload received from Voicenter. The structure depends on the trigger type but generally includes call details such as caller ID, call status, timestamps, and other relevant metadata.
If the trigger type is "phone," the output corresponds to query parameters sent via GET. For other types ("cdr" or "ivr"), the output corresponds to the POST body data.
No binary data output is produced by this node.
Dependencies
- Requires a publicly accessible webhook URL configured with the specified path and trigger type.
- No external API keys or credentials are required within the node itself since it passively receives data from Voicenter.
- The user must configure their Voicenter account to send webhook events to the generated URL.
Troubleshooting
- Webhook not triggering: Ensure that the webhook URL is correctly set in Voicenter and publicly accessible. Verify the
PathandTrigger Typematch the configuration in Voicenter. - No data received: Confirm that Voicenter is sending data for the selected trigger type. Check network logs or use tools like ngrok to inspect incoming requests.
- Unexpected data format: The node expects specific query or body parameters depending on the trigger type. If Voicenter changes its payload structure, the workflow may need adjustment.
- Response issues: If using "Using 'Respond to Webhook' node" mode, ensure that the subsequent node properly handles the response to avoid timeouts.
Links and References
- Voicenter Official Documentation (for configuring webhooks and understanding event types)
- n8n Webhook Node Documentation (general info on webhook triggers)