Overview
This node allows users to manage WhatsApp calls by rejecting incoming calls through the DinastiAPI service. It is particularly useful in scenarios where automated call handling is needed, such as when a user wants to programmatically decline calls based on certain conditions or during specific times (e.g., outside business hours). For example, a customer support system could automatically reject calls with a custom message when agents are unavailable.
Properties
| Name | Meaning |
|---|---|
| Call ID | The unique identifier of the call that you want to reject. |
| Call From | The JID (Jabber ID) of the caller, typically formatted like a WhatsApp number with domain. |
| Reject Type | The reason for rejecting the call. Options: Busy (line is busy), Declined (call declined), Unavailable (unable to answer). |
| Custom Message | An optional custom text message sent to the caller explaining why the call was rejected. |
Output
The node outputs JSON data representing the response from the DinastiAPI after attempting to reject the call. This includes details about the rejection request status. If an error occurs, the output will contain an error message describing what went wrong.
No binary data is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the DinastiAPI service.
- The node makes HTTP POST requests to the
/call/reject/sendendpoint of the DinastiAPI. - Proper configuration of the API credential within n8n is necessary for successful operation.
Troubleshooting
Common Issues:
- Invalid or missing Call ID or Call From values will cause the API request to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity issues can prevent the node from reaching the DinastiAPI server.
Error Messages:
- Errors returned from the API are captured and included in the node's output if "Continue On Fail" is enabled.
- Typical error messages might include invalid parameters or authorization failures.
Resolution Tips:
- Verify that the Call ID and Call From fields are correctly populated.
- Ensure the API key credential is valid and has the required permissions.
- Check network access and firewall settings to allow outbound requests to the DinastiAPI endpoint.
Links and References
- DinastiAPI Documentation (Replace with actual URL if available)
- WhatsApp JID Format Explanation