Actions53
- Instância Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Evento Actions
- Integração Actions
Overview
This node integrates with the Evolution API v2, enabling automation workflows to manage and interact with various resources such as instances, messages, groups, chats, events, and integrations. Specifically for the Evento resource with the RabbitMQ operation, it configures RabbitMQ event handling for a given instance.
Common scenarios where this node is beneficial include:
- Automating messaging workflows by sending texts, images, videos, or documents through WhatsApp instances.
- Managing WhatsApp groups by creating groups, updating group info, or managing members.
- Handling chat operations like checking if a number is on WhatsApp or marking messages as read/unread.
- Setting up event listeners via webhooks or RabbitMQ to react to real-time events.
- Integrating with external services like Chatwoot or bots for enhanced customer engagement.
Practical example for the Evento-RabbitMQ operation:
- You want to configure your WhatsApp instance to listen to message events via RabbitMQ queues, allowing your workflow to process incoming messages asynchronously and trigger further actions based on those events.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the WhatsApp instance to operate on. This identifies which instance the operation targets. |
(Note: Only the "Instance Name" property is relevant for the Evento-RabbitMQ operation as per the provided input properties.)
Output
The node outputs JSON data representing the result of the requested operation. For the Evento-RabbitMQ operation, the output typically confirms the successful configuration of RabbitMQ event handling for the specified instance.
The output JSON includes:
success: Boolean indicating if the operation was successful.message(optional): A descriptive message about the operation outcome.timestamp: ISO string timestamp when the operation completed.- Additional fields may be present depending on the API response.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Evolution API v2.
- The node uses HTTP requests to the Evolution API endpoints.
- Proper configuration of the Evolution API credentials in n8n is necessary.
- For RabbitMQ event handling, the target WhatsApp instance must support and be configured for RabbitMQ integration on the Evolution platform.
Troubleshooting
Common issues:
- Incorrect or missing instance name will cause the API call to fail.
- Invalid or expired API authentication token will result in authorization errors.
- Network connectivity problems can prevent communication with the Evolution API.
- Misconfiguration of RabbitMQ on the Evolution platform side may cause event setup failures.
Error messages:
- Authorization errors: Check that the API key credential is valid and has proper permissions.
- "Instance not found": Verify the instance name is correct and exists.
- Timeout or network errors: Ensure stable internet connection and that the Evolution API endpoint is reachable.
- JSON parsing errors: Usually indicate unexpected API responses; check API status or contact support.
Links and References
- Evolution API Documentation (hypothetical link, replace with actual)
- n8n HTTP Request Node Documentation
- RabbitMQ Official Site
If you need details on other resources or operations, please provide their names.