Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

This node interacts with the Evolution API, specifically focusing on managing RabbitMQ event integration within the "Event" resource. It allows users to enable or disable RabbitMQ integration and check its status for a given instance. This is useful in scenarios where you want to control event-driven messaging through RabbitMQ, such as enabling real-time updates or monitoring event flows.

Practical examples include:

  • Enabling RabbitMQ events for an instance to receive notifications about chat updates or message changes.
  • Disabling RabbitMQ integration when event streaming is no longer needed.
  • Checking the current RabbitMQ configuration status for troubleshooting or auditing purposes.

Properties

Name Meaning
Instance Name The name of the instance that will send the message via RabbitMQ.
What Do You Want To Do Choose between enabling/disabling RabbitMQ integration ("Set RabbitMQ") or checking its status ("Check RabbitMQ").
Enable RabbitMQ Boolean flag to enable (true) or disable (false) the RabbitMQ integration (only when setting).
Events Select one or more specific RabbitMQ event types to enable or listen for, such as CALL, CHATS_DELETE, MESSAGES_SET, etc.

Output

The node outputs JSON data representing the result of the chosen operation:

  • For setting RabbitMQ integration, the output typically confirms whether the integration was successfully enabled or disabled along with the selected events.
  • For checking RabbitMQ, the output provides the current status and configuration details of the RabbitMQ integration for the specified instance.

No binary data output is involved.

Dependencies

  • Requires an active connection to the Evolution API, authenticated via an API key credential configured in n8n.
  • The node depends on the Evolution API endpoint at https://doc.evolution-api.com/api-reference.
  • Proper permissions and valid instance names are necessary to perform operations.

Troubleshooting

  • Common issues:

    • Invalid or missing instance name may cause errors or no action.
    • Incorrect API credentials or expired tokens will lead to authentication failures.
    • Selecting unsupported events or invalid combinations might cause the API to reject requests.

  • Error messages:

    • "Operation not supported." indicates that the requested operation is not implemented for the selected resource.
    • Authentication errors suggest checking API key validity and permissions.
    • Validation errors often relate to missing required parameters like instance name or event selections.

To resolve these, verify all input parameters, ensure correct API credentials are set up in n8n, and confirm the instance exists and supports RabbitMQ integration.

Links and References

Discussion