Actions59
- Blacklist Actions
- Call Actions
- Client Actions
- Entity Actions
- Import Actions
- Lead Actions
- PBX Actions
- Queue Actions
- Report Actions
- Get Daily Managements
- Get Dropped Calls
- Get Summary
- Get Time Slot
- Get Users Management
- Get Calls
- Get Client Management
- Get Forms
- Get Incoming Call
- Get IVR Survey
- Get Log ACW
- Get Managements by ACW
- Get Managements per Hour
- Get Messaging Tickets
- Get PDP Control
- Get List PDP
- Get PDP Ranking
- Get Phones
- Get Platform Detailed
- Get Platform Summarized
- Get Product Managements
- Get Products
- Get Progress Managements
- Get Strategies
- Get Tickets Tracking
- Sequence Actions
- Template Actions
- Ticket Actions
- User Actions
Blacklist → Block One
AI-generatedOverview
This node interacts with the Beex Contact Center API to block a phone number by adding it to a blacklist. It is useful in scenarios where you want to prevent specific phone numbers from contacting or being contacted through the system, such as blocking spam or unwanted calls. For example, a call center can use this node to automatically block numbers reported as spam or fraudulent.
Use Case Examples
- Blocking a phone number from a specific country with observations and channel details to prevent further calls or messages from that number.
- Adding multiple phone numbers to the blacklist in a batch process to maintain a clean contact list.
Properties
| Name | Meaning |
|---|---|
| Country ID | The ID of the country associated with the phone number to block. |
| Phone Number | The phone number to be blocked. |
| Observations | Additional notes or considerations related to the blocking of the phone number. |
| Channel ID | The ID of the communication channel through which the blocking applies. |
| Custom Channels | Custom channel IDs separated by commas, specifying additional channels for blocking. |
Output
JSON
json- The response from the Beex API after attempting to block the phone number, which may include success confirmation or error details.
Dependencies
- Beex Contact Center API with an API key credential
Troubleshooting
- Common issues include invalid or missing parameters, which result in error messages from the API. Ensure all required fields (Country ID, Phone Number, Observations, Channel ID, Custom Channels) are correctly provided.
- API authentication errors may occur if the API key credential is missing or invalid. Verify the API key is correctly configured in the node credentials.
- Network or connectivity issues can cause request failures. Check network access to the Beex API endpoint.
- Error messages from the API are parsed and presented with details to help identify the cause, such as status codes and error messages from the response body.