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-related resources. Specifically, for the Blacklist resource and the addToBlacklist operation, it allows users to add one or multiple phone numbers to a blacklist. This is useful in scenarios where you want to block unwanted calls or messages from specific numbers.
Practical examples include:
- Automatically blocking spam callers by adding their numbers to the blacklist.
- Managing a list of blocked contacts in a call center environment.
- Preventing calls from certain customers or vendors based on business rules.
Properties
| Name | Meaning |
|---|---|
| Phones | List of phone entries to blacklist. Each entry includes: - Phone: Phone number in E.164 format (required). - Name: Optional name associated with the blocked number. |
| Merge JSON parameters | Boolean flag to enable merging additional parameters via JSON using lodash's merge function. When enabled, this allows appending or updating parameters dynamically. |
| JSON | Raw JSON input to specify additional parameters when "Merge JSON parameters" is enabled. This JSON will be merged into the request payload. |
Output
The node outputs JSON data representing the result of the add-to-blacklist operation as returned by the Voicenter API. The exact structure depends on the API response but typically includes confirmation of the blacklisted numbers and any relevant metadata.
If the node supports binary data output (not indicated here), it would represent related binary content such as files or media, but this operation primarily deals with JSON data.
Dependencies
- Requires an active connection to the Voicenter API via an API key credential configured in n8n.
- Uses the Voicenter API client internally to perform operations.
- Optionally uses lodash's
mergefunction to combine JSON parameters if enabled.
Troubleshooting
- Invalid phone number format: Ensure all phone numbers are provided in E.164 format (e.g., +1234567890). Incorrect formats may cause API errors.
- Missing required fields: The "Phones" property must contain at least one valid phone entry; otherwise, the node will fail.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- JSON merge issues: If enabling "Merge JSON parameters," ensure the JSON syntax is valid to avoid parsing errors.
- Network or API downtime: Temporary connectivity issues with the Voicenter API can cause failures; retry after some time.
Links and References
- Voicenter API Documentation (replace with actual URL)
- E.164 Phone Number Format
- Lodash merge documentation