DinastiAPI Call icon

DinastiAPI Call

Manage WhatsApp calls using DinastiAPI API
Join our community

Overview

This node allows users to reject incoming WhatsApp calls programmatically using the DinastiAPI service. It is useful in scenarios where automated call handling is needed, such as when a user is unavailable, busy, or wants to decline calls with a custom message. For example, a business could automatically reject calls outside of working hours with a polite message explaining unavailability.

Properties

Name Meaning
Call ID The unique identifier of the call 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 a JSON object representing the response from the DinastiAPI after attempting to reject the call. This includes confirmation details or error messages if the rejection failed. The output is structured as an array of JSON objects, each corresponding to an input item processed.

If an error occurs and "Continue On Fail" is enabled, the output will contain an error object with the error message for that specific item.

Dependencies

  • Requires an API key credential for authenticating with the DinastiAPI service.
  • The node makes HTTP POST requests to the /call/reject/send endpoint of the DinastiAPI.
  • Proper configuration of the DinastiAPI credentials within n8n is necessary.

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 problems can prevent the node from reaching the DinastiAPI server.

  • Error messages:

    • Errors returned by the API are passed through in the output JSON under an error field.
    • If the node throws an error, verify that all required parameters are correctly set and that the API credentials are valid.
    • Enabling "Continue On Fail" allows the workflow to proceed even if some calls fail, providing error details per item.

Links and References

  • DinastiAPI Documentation (example placeholder link)
  • WhatsApp Business API documentation for call management (for conceptual understanding)

Discussion