Evolution API icon

Evolution API

Interact with Evolution API

Overview

This node interacts with the Evolution API to manage RabbitMQ event integration for a specified instance. It allows users to enable or disable RabbitMQ integration and select specific events to be handled via RabbitMQ. This is useful for automating workflows that depend on real-time event messaging through RabbitMQ, such as monitoring chat updates, message events, or connection changes in an application environment.

Use Case Examples

  1. Enable RabbitMQ integration for an instance to listen for chat and message events.
  2. Disable RabbitMQ integration for an instance to stop receiving event messages.
  3. Check the current RabbitMQ integration status for an instance.

Properties

Name Meaning
Instance Name The name of the instance that will send the message, used to identify which instance's RabbitMQ integration is being managed.
What Do You Want To Do Select whether to enable/disable RabbitMQ integration or check the current RabbitMQ status.
Enable RabbitMQ Boolean flag to enable or disable RabbitMQ integration when setting RabbitMQ.
Events List of RabbitMQ events to enable or listen for when RabbitMQ integration is enabled.

Output

JSON

  • status - The status of the RabbitMQ integration operation (e.g., enabled, disabled, or current status).
  • events - The list of RabbitMQ events configured or retrieved for the instance.
  • instanceName - The name of the instance for which the RabbitMQ integration is managed.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API.

Troubleshooting

  • If the node throws an 'Unsupported operation' error, verify that the selected operation and resource are correct and supported by the node.
  • Ensure the 'Instance Name' is correctly specified and matches an existing instance in the Evolution API system.
  • Check that the API credentials are valid and have the necessary permissions to manage RabbitMQ integration.
  • If enabling RabbitMQ fails, verify network connectivity and that the Evolution API service is reachable.

Discussion