Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
This node interacts with the Evolution API, specifically focusing on managing RabbitMQ event integration for an "Event" resource. It allows users to enable or disable RabbitMQ integration and verify its status for a given instance. This is useful in scenarios where you want to control event-driven messaging through RabbitMQ, such as activating event notifications or checking if the RabbitMQ setup is correctly configured.
Practical examples include:
- Enabling RabbitMQ events for a specific instance to receive real-time updates about calls, chats, messages, contacts, groups, and other event types.
- Disabling RabbitMQ integration when event streaming is no longer needed.
- Verifying the current RabbitMQ configuration status to troubleshoot connectivity or integration issues.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance that will send the message. |
| What Do You Want to Do | Choose between enabling/disabling RabbitMQ integration ("Definir RabbitMQ") or verifying RabbitMQ status ("Verificar RabbitMQ"). |
| Ativar RabbitMQ | Boolean flag to enable (true) or disable (false) the RabbitMQ integration. |
| Eventos | Select one or more event types to activate for RabbitMQ integration. Available options include: CALL, CHATS_DELETE, CHATS_SET, CHATS_UPDATE, CHATS_UPSERT, CONNECTION_UPDATE, CONTACTS_SET, CONTACTS_UPDATE, CONTACTS_UPSERT, GROUP_PARTICIPANTS_UPDATE, GROUP_UPDATE, GROUPS_UPSERT, LABELS_ASSOCIATION, LABELS_EDIT, MESSAGES_DELETE, MESSAGES_SET, MESSAGES_UPDATE, MESSAGES_UPSERT, PRESENCE_UPDATE, QRCODE_UPDATED, SEND_MESSAGE, TYPEBOT_CHANGE_STATUS, TYPEBOT_START. |
Output
The node outputs JSON data representing the result of the requested operation on the RabbitMQ integration. This typically includes confirmation of the action taken (enabled/disabled), the current status of RabbitMQ integration, or details about the selected events.
If binary data were involved, it would represent related files or media, but this node focuses on JSON responses related to event integration status and configuration.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node depends on the Evolution API endpoint at
https://doc.evolution-api.com/api-reference. - No additional external services are required beyond the Evolution API and RabbitMQ infrastructure managed by it.
Troubleshooting
Common Issues:
- Incorrect or missing instance name may cause failures in identifying which instance to configure.
- Selecting unsupported operations or event types could lead to errors.
- Network or authentication issues with the Evolution API can prevent successful requests.
Error Messages:
"Operação não suportada."indicates the chosen operation is not supported for the specified resource. Verify that the operation and resource names are correct.- Authentication errors suggest invalid or missing API credentials; ensure the API key is properly configured.
- Connectivity errors may require checking network access to the Evolution API endpoint.
Links and References
- Evolution API Documentation (official API reference)
- RabbitMQ official site for understanding event messaging: https://www.rabbitmq.com/
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.