Actions64
- Instancia Actions
- Mensaje Actions
- Grupo Actions
- Crear Grupo
- Actualizar Imagen Del Grupo
- Actualizar Nombre Del Grupo
- Actualizar Descripción Del Grupo
- Actualizar Configuraciones
- Actualizar Miembros
- Buscar Enlace De Invitación
- Revocar Enlace De Invitación
- Enviar Enlace De Invitación
- Buscar Grupos
- Encontrar Participantes
- Mensajes Temporales
- Unirse Al Grupo
- Salir Del Grupo
- Chat Actions
- Perfil Actions
- Evento Actions
- Integración Actions
Overview
This node, named "Evolution API," is designed to interact with the Evolution API service. Specifically for the "Evento" resource and the "RabbitMQ" operation, it allows users to manage RabbitMQ integration related to event messaging. Users can enable or disable RabbitMQ integration or verify existing RabbitMQ configurations.
Common scenarios include:
- Activating RabbitMQ to start sending event messages from a specified instance.
- Disabling RabbitMQ integration when event messaging is no longer needed.
- Checking the current status or configuration of RabbitMQ integration.
Practical example:
- A user wants to enable RabbitMQ on their event system to receive real-time updates about chat messages or group changes. They specify the instance name and select which events should trigger messages sent via RabbitMQ.
Properties
Name | Meaning |
---|---|
Nombre De La Instancia | The name of the instance that will send the message. |
Qué Desea Hacer | Choose between activating/deactivating RabbitMQ ("Definir RabbitMQ") or verifying existing RabbitMQ ("Verificar RabbitMQ"). |
Activar RabbitMQ | Boolean option to enable (true ) or disable (false ) the RabbitMQ integration (only when setting RabbitMQ). |
Eventos | Select one or more event types to be handled by RabbitMQ. 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 include confirmation of enabling/disabling RabbitMQ, details about the current RabbitMQ configuration, or verification results.
No binary data output is indicated in the source code or properties.
Dependencies
- Requires an API key credential to authenticate with the Evolution API service.
- The node uses the base URL
https://doc.evolution-api.com/api-reference
for API requests. - No additional external dependencies are explicitly required beyond this API access.
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 you select valid combinations of resource and operation.
- Missing Required Parameters: The "Nombre De La Instancia" property is required. Omitting it may cause errors or failed requests.
- API Authentication Issues: Incorrect or missing API credentials will prevent successful communication with the Evolution API.
- Event Selection: When enabling RabbitMQ, if no events are selected, the integration might not behave as expected. Make sure to select relevant events.
Links and References
- Evolution API Documentation (base URL used by the node)
- RabbitMQ official site for understanding event messaging concepts: https://www.rabbitmq.com/
If you need further details on other resources or operations, please provide their names.