Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
This node integrates with the Evolution API to manage event-related operations specifically for RabbitMQ messaging. It allows users to enable or disable RabbitMQ integration and check its status for a given instance. This is useful in scenarios where you want to control or monitor message queueing behavior within an event-driven system, such as enabling real-time notifications or synchronizing data across services using RabbitMQ.
Practical examples include:
- Enabling RabbitMQ to start sending event messages from a specified instance.
- Disabling RabbitMQ integration when message queuing is no longer needed.
- Checking the current status of RabbitMQ integration to verify connectivity or configuration.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance that will send the message via RabbitMQ. |
| Action | Choose between "Set RabbitMQ" (enable/disable integration) or "Check RabbitMQ" (check current status). |
| Enable RabbitMQ | Boolean option to enable (true) or disable (false) RabbitMQ integration (only when setting RabbitMQ). |
| Events | Select one or multiple event types to be handled by RabbitMQ integration, e.g., CALL, MESSAGES_SET, etc. |
Output
The node outputs a JSON array containing the result of the selected operation on RabbitMQ. This typically includes confirmation of the action taken (enabled/disabled), the current status of RabbitMQ integration, or details about the events configured. The exact structure depends on the API response but generally reflects success or failure states and relevant metadata.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- Needs network access to
https://doc.evolution-api.com/api-referenceor the actual Evolution API endpoint. - Proper configuration of the instance name and RabbitMQ settings within the Evolution API environment.
Troubleshooting
- Unsupported operation error: If the node throws an error stating the operation is unsupported, ensure that the Resource is set to "events-api" and Operation to "rabbitmq" with a valid action ("setRabbitMQ" or "findRabbitMQ").
- Missing or invalid instance name: The node requires a valid instance name; leaving it empty or incorrect may cause failures.
- API authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
- Network issues: Connectivity problems to the Evolution API endpoint can cause timeouts or failures; check firewall and proxy settings.
Links and References
- Evolution API Documentation (official API reference)
- RabbitMQ official site for understanding message queue concepts: https://www.rabbitmq.com/
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.