DinastiAPI Chat icon

DinastiAPI Chat

Perform chat operations with DinastiAPI WhatsApp API

Overview

This node integrates with the DinastiAPI WhatsApp API to perform various chat-related operations. Specifically, the "React to Message" operation allows users to send emoji reactions to WhatsApp messages or remove existing reactions. This is useful for automating message interactions, such as acknowledging receipt, expressing emotions, or managing message feedback without sending a new text message.

Practical examples include:

  • Automatically reacting with a thumbs-up emoji when a customer sends a confirmation message.
  • Removing a reaction if a condition changes in your workflow.
  • Reacting with different emojis based on sentiment analysis of incoming messages.

Properties

Name Meaning
Phone Number The phone number associated with the message to react to. Can be prefixed with "me:" to indicate your own message. Example: 5491155553934 or me:5491155553934.
Reaction The emoji to use as a reaction. Leave empty to remove an existing reaction. Examples: ❤️, 👍, 😂.
Message ID The identifier of the message to react to. Prefix with "me:" if it is your own message. Example: me:3EB06F9067F80BAB89FF.

Output

The node outputs JSON data representing the response from the DinastiAPI WhatsApp API after attempting to react to a message. The structure typically includes details about the success or failure of the reaction request.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the DinastiAPI WhatsApp API.
  • Requires an API key credential configured in n8n for authenticating requests to DinastiAPI.
  • The node uses HTTP POST requests to the /chat/react endpoint of the API.

Troubleshooting

  • Common issues:

    • Invalid or missing message ID or phone number can cause the reaction to fail.
    • Using an incorrect prefix (missing "me:" when reacting to own messages) may result in errors.
    • Network or authentication failures with the DinastiAPI service will prevent reactions from being sent.
  • Error messages:

    • Errors returned from the API will be included in the node's output if "Continue On Fail" is enabled.
    • Typical error messages might relate to invalid parameters or authorization failures.
  • Resolutions:

    • Verify that the phone number and message ID are correct and properly formatted.
    • Ensure the API key credential is valid and has necessary permissions.
    • Check network connectivity and API service status.

Links and References

Discussion