Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API" is designed to interact with the Evolution API, providing a way to perform various operations on different resources. Specifically for the resource "Evento" and operation "RabbitMQ," it allows users to manage RabbitMQ integration settings related to event messaging. This includes enabling or disabling RabbitMQ integration and checking its status.
Common scenarios where this node is beneficial include:
- Configuring event-driven workflows that rely on RabbitMQ messaging.
- Enabling or disabling RabbitMQ event notifications dynamically.
- Monitoring the current state of RabbitMQ integration within an application.
For example, a user might enable RabbitMQ to start receiving real-time updates about chat messages or group participant changes, or disable it temporarily during maintenance.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instancia | The name of the instance that will send the message. |
| O Que Deseja Fazer | Choose between activating/deactivating RabbitMQ integration ("Definir RabbitMQ") or checking its status ("Verificar RabbitMQ"). |
| Ativar RabbitMQ | Boolean flag to enable (true) or disable (false) the RabbitMQ integration (only shown when setting RabbitMQ). |
| Eventos | List of event types to subscribe to for RabbitMQ messages. 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 RabbitMQ operation. This could be confirmation of enabling/disabling RabbitMQ integration or details about the current RabbitMQ status. The output is structured as an array of JSON objects, each containing relevant information returned by the Evolution API regarding the RabbitMQ configuration or status.
There is no indication that the node outputs binary data.
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. - Proper configuration of the API credentials in n8n is necessary for successful requests.
Troubleshooting
- Unsupported Operation Error: If the selected operation is not supported for the chosen resource, the node throws an error stating the operation is not supported. Ensure the correct resource and operation names are used.
- API Authentication Failures: Errors may occur if the API key credential is missing or invalid. Verify that the API key is correctly configured in n8n.
- Network Issues: Connectivity problems to the Evolution API endpoint can cause failures. Check network access and endpoint availability.
- Invalid Property Values: Providing empty or incorrect values for required properties like "Nome Da Instancia" may lead to errors. Always provide valid inputs.
Links and References
- Evolution API Documentation (official API reference)
- RabbitMQ Official Site (for understanding RabbitMQ concepts)
This summary is based solely on static analysis of the provided source code and property definitions.