Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The node "Evolution API" provides integration with the Evolution API, allowing users to perform various operations on different resources. Specifically for the resource "Evento" and operation "RabbitMQ," it enables managing RabbitMQ integration settings related to event messaging. This includes activating or deactivating RabbitMQ integration and verifying 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.
  • Checking the current state of RabbitMQ integration for monitoring or troubleshooting purposes.

For example, a user can enable RabbitMQ to receive real-time updates about chat events or message changes, or disable it when such notifications are not needed.

Properties

Name Meaning
Nome Da Instancia The name of the instance that will send the message.
O Que Deseja Fazer Choose between enabling/disabling 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 via 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 typically includes confirmation of the action taken (e.g., whether RabbitMQ was enabled or disabled) or the current status information when verifying RabbitMQ.

If the node interacts with binary data, it is not indicated in the provided code or properties, so output is expected to be purely JSON.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API.
  • The node depends on the Evolution API service being accessible and properly configured.
  • RabbitMQ server or integration must be set up externally; this node manages its activation and event subscriptions via the API.

Troubleshooting

  • Unsupported Operation Error: If an unsupported operation or resource is specified, the node throws an error indicating the operation is not supported. Ensure the resource is "events-api" and operation is "rabbitmq" for this functionality.
  • Missing Required Parameters: The "Nome Da Instancia" property is required. Omitting it may cause errors or failed requests.
  • API Authentication Issues: Invalid or missing API credentials will prevent successful communication with the Evolution API.
  • Event Subscription Errors: Selecting invalid or unsupported event types could lead to unexpected behavior or no events being received.

To resolve these issues:

  • Verify all required parameters are correctly filled.
  • Confirm API credentials are valid and have necessary permissions.
  • Check that the Evolution API endpoint and RabbitMQ integration are operational.

Links and References

Discussion