Actions10
- clickToCall Actions
- Pop-Up Screen Actions
- callLog Actions
- External IVR Actions
- CDR Notifications Actions
- Dialer Actions
- Blacklist Actions
Overview
The node integrates with the Voicenter API to manage telephony dialer operations. Specifically, the addCall operation under the Dialer resource allows users to programmatically add a call target to a campaign for outbound dialing.
This node is beneficial in scenarios such as:
- Automating outbound call campaigns by adding new call targets dynamically.
- Integrating call scheduling and prioritization into CRM or marketing workflows.
- Enriching call data with custom metadata for enhanced call logging and pop-up information during calls.
For example, a user can add a phone number to a specific campaign with a scheduled call time and custom caller ID, enabling targeted and timed outreach efforts.
Properties
| Name | Meaning |
|---|---|
| Campaign | The unique identifier of the campaign to which the call will be added. This ID is obtained from the GetCampaignList method (version 7.1). Required field. |
| Target | The destination phone number to call. Must include the international prefix except for Israeli numbers where it is optional. Required field. |
| Additional Fields | Optional extra parameters to customize the call: - Customer Name: Name of the call target. - Caller ID: Phone number displayed to the call recipient; must belong to your Voicenter account. - Priority: Numeric priority; higher values dial first. - Custom Data: User-defined key-value pairs associated with the call for pop-ups and logs. - Originate Time: Epoch timestamp to schedule the call for a future date/time. - Is Date Local: Boolean indicating if the originate time is local time (recommended true). - Ignore Dnc Status: Boolean to override Do-Not-Call restrictions for Israeli destinations if enabled in your account. |
Output
The node outputs JSON data representing the result of the addCall API request. This typically includes confirmation details such as call ID, status, and any error messages returned by the Voicenter API.
If the node supports binary data output (not indicated here), it would represent media or call recordings related to the call, but this operation primarily deals with JSON responses.
Dependencies
- Requires an active Voicenter API credential configured in n8n, including necessary authentication tokens or API keys.
- Depends on the Voicenter API service being accessible and operational.
- Uses internal client and state management classes to handle API requests and response parsing.
Troubleshooting
- Invalid Campaign ID: Ensure the campaign identifier is correct and exists in your Voicenter account.
- Incorrect Phone Number Format: Verify that the target phone number includes the proper international prefix unless calling Israeli numbers.
- Caller ID Not Authorized: The Caller ID must be a phone number registered in your Voicenter account; otherwise, the call may be rejected.
- Scheduling Errors: When using
Originate Time, ensure it is provided together withIs Date Local. Incorrect timestamps or mismatched time zone flags can cause scheduling failures. - Do-Not-Call Restrictions: If calls are blocked due to DNC settings, use the
Ignore Dnc Statusflag only if you have permission to override these restrictions. - API Credential Issues: Authentication failures indicate misconfigured or expired credentials; reconfigure the API key/token in n8n.
Links and References
- Voicenter API Documentation (replace with actual URL)
- Epoch Time Converter – Useful for setting
Originate Time. - International Phone Number Formats – Guidelines for formatting phone numbers with country codes.