Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The Evento - RabbitMQ operation in the custom n8n node "Evolution API" allows users to manage and interact with RabbitMQ integration for a specified instance. This includes enabling or disabling RabbitMQ event forwarding, as well as checking the current status of the RabbitMQ integration for an instance.

Typical use cases include:

  • Activating or deactivating RabbitMQ event streaming for a messaging or automation platform.
  • Verifying if RabbitMQ is currently enabled for a given instance.
  • Selecting specific events that should be forwarded to RabbitMQ.

Practical examples:

  • An administrator wants to enable RabbitMQ for a WhatsApp integration and only forward message-related events.
  • A developer needs to check if RabbitMQ is active before deploying new automations.

Properties

Display Name Type Description
Nome Da Instancia String Digite o nome da instância que vai enviar a mensagem (Name of the instance sending messages).
O Que Deseja Fazer Options Escolha entre ativar/desativar RabbitMQ ou verificar o RabbitMQ (Choose to set or check RabbitMQ).
Options:
  • Definir RabbitMQ (setRabbitMQ)
  • Verificar RabbitMQ (findRabbitMQ)
Ativar RabbitMQ Boolean Whether to enable or disable integration with RabbitMQ.
Shown only when "Definir RabbitMQ" is selected.
Eventos MultiOptions Select which events to forward to RabbitMQ.
Shown only when "Definir RabbitMQ" is selected.
Possible values 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 output is a JSON object (or array of objects) containing the result of the requested operation. The structure will depend on whether you are setting or checking the RabbitMQ integration:

  • For Definir RabbitMQ (setRabbitMQ):
    The output typically confirms the activation/deactivation status and lists the events configured.
  • For Verificar RabbitMQ (findRabbitMQ):
    The output provides the current status of RabbitMQ integration for the specified instance, including which events are enabled.

Example output (structure may vary):

[
  {
    "instanceName": "my-instance",
    "rabbitMQEnabled": true,
    "events": ["MESSAGES_SET", "SEND_MESSAGE"]
  }
]

Note: The actual field names and structure may differ based on the backend API response.

Dependencies

  • External Service: Requires access to the Evolution API service.
  • API Key/Credentials: Needs valid credentials for the "evolutionApi" as configured in n8n.
  • Environment: No special environment variables required beyond standard n8n credential setup.

Troubleshooting

Common issues:

  • Invalid Credentials: If the provided API key is incorrect or missing, authentication errors will occur.
  • Unsupported Operation: If an unsupported resource or operation is selected, the node throws an error:
    Operação não suportada. A função "<operation>" para o recurso "<resource>" não é suportada!
    Resolution: Double-check that you have selected a valid combination of Resource and Operation.
  • Missing Required Fields: If "Nome Da Instancia" is not provided, the node will fail validation.
  • Network/API Errors: Connectivity issues or downtime on the Evolution API side can cause failures.

Links and References

Discussion