Evolution API icon

Evolution API

Interact with Evolution API
Join our community

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 to reduce system load.

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.
Eventos List of event types to subscribe to in 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 supports binary data output, it is not indicated in the provided code or properties, so the output is primarily JSON structured data.

Dependencies

  • Requires an API key credential to authenticate with the Evolution API.
  • Depends on the Evolution API service being accessible and properly configured.
  • No additional external dependencies or environment variables are explicitly required based on the provided code.

Troubleshooting

  • Unsupported Operation Error: If an unsupported operation is selected, the node throws an error indicating the operation is not supported. Ensure the operation and resource names are correctly specified.
  • Missing Required Parameters: The "Nome Da Instancia" property is required; omitting it may cause errors or unexpected behavior.
  • API Authentication Issues: Failure to provide valid API credentials will prevent successful communication with the Evolution API.
  • Event Subscription Issues: Selecting no events or invalid event names might lead to no messages being received or processed.

To resolve these issues:

  • Verify all required parameters are set.
  • Confirm API credentials are valid and have necessary permissions.
  • Use only supported event names as listed in the properties.
  • Check network connectivity to the Evolution API endpoint.

Links and References

Discussion