Evolution API Direct icon

Evolution API Direct

Interact with Evolution API using direct URL and API Key

Actions64

Overview

The node "Evolution API Direct" allows interaction with the Evolution API by specifying a resource and operation, using a direct URL and an API key for authentication. Specifically, for the Resource "Evento" and Operation "RabbitMQ," it enables users to manage RabbitMQ integration settings within the Evolution API environment. This includes activating or deactivating RabbitMQ integration and verifying its current status.

Typical use cases include:

  • Enabling RabbitMQ event streaming for real-time updates.
  • Disabling RabbitMQ integration when not needed.
  • Checking the current RabbitMQ configuration status.

For example, a user might enable RabbitMQ to receive live event notifications such as message updates or group changes, facilitating automation workflows that react instantly to these events.

Properties

Name Meaning
Server URL The full URL of the Evolution API server to connect to (e.g., https://api.exemplo.com).
API Key The API key credential required to authenticate requests to the Evolution API instance or globally.
Nome Da Instancia The name of the specific instance that will send the RabbitMQ messages.
O Que Deseja Fazer Choose between two actions: "Definir RabbitMQ" (set/enable/disable RabbitMQ) or "Verificar RabbitMQ" (check status).
Ativar RabbitMQ Boolean flag to enable (true) or disable (false) the RabbitMQ integration (only shown if setting RabbitMQ).
Eventos Select one or more event types to be handled by RabbitMQ integration. 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 a JSON array containing the result of the requested operation on the RabbitMQ integration. The structure depends on the chosen action:

  • For "Definir RabbitMQ" (setRabbitMQ), the output typically confirms whether RabbitMQ was successfully enabled or disabled along with any relevant status messages.
  • For "Verificar RabbitMQ" (findRabbitMQ), the output provides the current configuration and status details of the RabbitMQ integration.

No binary data output is indicated in the source code.

Dependencies

  • Requires access to the Evolution API endpoint specified by the "Server URL."
  • Requires a valid API key credential for authentication.
  • The node depends on the Evolution API's internal handling of RabbitMQ integration.
  • No additional external services or environment variables are explicitly required beyond the API key and server URL.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API key may cause authentication failures.
    • Invalid or unreachable Server URL will prevent connection to the Evolution API.
    • Selecting unsupported operations or resources will throw errors indicating unsupported functions.
    • Misconfiguration of instance name or event selections may lead to unexpected behavior or no events being received.

  • Error Messages:

    • "Operação não suportada." indicates the selected operation is not supported for the given resource.
    • Network or authentication errors from the Evolution API will surface as standard HTTP errors; ensure credentials and URLs are correct.

  • Resolutions:

    • Verify API key validity and permissions.
    • Confirm the Server URL is correct and accessible.
    • Double-check the instance name matches the configured Evolution API instance.
    • Ensure the chosen operation matches the resource and is supported.

Links and References

Discussion