Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node provides an interface to interact with the Evolution API, specifically allowing users to send reactions (emoji responses) to messages within a chat. This is useful in scenarios where automated or programmatic feedback on messages is needed, such as acknowledging receipt, expressing approval, or other quick emotional responses without sending a full message.
For example, you might use this node to automatically react with a thumbs-up emoji to confirm that a support ticket message has been seen, or to add a smiley reaction to customer feedback messages.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Chat Number | The identifier (number) of the chat where the target message resides. |
| Message ID | The unique identifier of the message to which the reaction will be added. |
| Own Message | Boolean indicating whether the message is sent by yourself (true) or someone else (false). |
| Reaction Emoji | The emoji character to use as the reaction (e.g., 👍). |
Output
The node outputs a JSON array containing the result of the reaction operation. The exact structure depends on the Evolution API response but typically includes confirmation of the reaction being applied, possibly including status or updated message metadata.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n for the Evolution API.
- The base URL for requests is set to
https://doc.evolution-api.com/api-reference.
Troubleshooting
- Operation not supported error: If the specified resource or operation is not recognized, the node throws an error stating the function is unsupported. Ensure the resource is "messages-api" and operation is "send-reaction".
- Missing required parameters: All properties marked as required must be provided; otherwise, the node will fail.
- API connectivity issues: Network problems or invalid credentials can cause failures. Verify API keys and network access.
- Invalid message or chat IDs: Providing incorrect identifiers may result in errors from the API about missing messages or chats.
Links and References
- Evolution API Documentation (base URL used by the node)