Wappfy icon

Wappfy

Interact with WhatsApp through Wappfy API

Message → Send Reaction

AI-generated

Overview

This node enables interaction with WhatsApp via the Wappfy API, specifically allowing users to send reactions (emoji) to existing WhatsApp messages. The "Send Reaction" operation lets you add an emoji reaction to a message identified by its unique message ID.

Common scenarios for this node include:

  • Automatically reacting to incoming messages in customer support workflows.
  • Adding emoji reactions as acknowledgments or feedback in group chats.
  • Enhancing chatbot interactions by sending reactions based on message content.

Example: Reacting with a thumbs-up emoji ("👍") to a specific message to indicate approval or confirmation.

Properties

Name Meaning
Message ID The unique identifier of the message to which you want to react.
Reaction Emoji The emoji character to use as the reaction (e.g., 👍, ❤️, 😂).

Output

The node outputs the JSON response returned by the Wappfy API after sending the reaction. This typically includes details about the success or failure of the reaction request and any relevant metadata from the API.

No binary data output is produced by this operation.

Dependencies

  • Requires a valid Wappfy API credential with an API key and instance name configured in n8n.
  • The node makes HTTP requests to the Wappfy API endpoints.
  • Network connectivity to the Wappfy API service is necessary.

Troubleshooting

  • Invalid Message ID: If the provided message ID does not exist or is incorrect, the API may return an error indicating the message was not found. Verify the message ID is correct.
  • Invalid Emoji: Using unsupported or malformed emoji characters might cause the API to reject the reaction. Use standard Unicode emoji.
  • Authentication Errors: Ensure the API key credential is correctly set up and has permissions to send reactions.
  • API Rate Limits: Excessive requests may be throttled by the Wappfy API. Implement retries or backoff if needed.
  • Network Issues: Connectivity problems will cause request failures. Check network access and proxy settings if applicable.

Error messages from the API are passed through in the node's output JSON under an error field if continueOnFail is enabled.

Links and References

Discussion