Evolution API

Interagir com a Evolution API v2
Join our community

Actions53

Overview

This node integrates with the Evolution API v2, enabling automation and management of various messaging and communication tasks. It supports multiple resources such as instances, messages, groups, chats, events, and integrations. Specifically, for the "Integração" (Integration) resource with the "Flowise" operation, it allows configuring Flowise integration within an instance.

Common scenarios where this node is beneficial include:

  • Automating WhatsApp message sending and management.
  • Managing chat groups and participants.
  • Setting up webhooks or external service integrations like Chatwoot, Evolution Bot, Typebot, Dify, and Flowise.
  • Controlling instance lifecycle and connection states.

Practical example:

  • A user can configure a Flowise integration for a specific instance by providing the instance name and relevant Flowise configuration parameters, enabling automated workflows that interact with the Evolution platform through Flowise.

Properties

Name Meaning
Instance Name The name of the instance to which the Flowise integration will be configured. This is required.

(Note: Since only the "Integração" resource and "Flowise" operation are requested, only the "Instance Name" property applies here.)

Output

The node outputs JSON data representing the result of the API call to configure the Flowise integration. The output includes:

  • success: Boolean indicating if the operation was successful.
  • Other fields depend on the API response but typically include confirmation details of the integration setup.
  • timestamp: ISO string timestamp when the operation was completed.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Evolution API.
  • The node uses the Evolution API v2 endpoints.
  • Proper configuration of the Evolution API credentials in n8n is necessary.
  • Network access to the Evolution API endpoints must be available.

Troubleshooting

  • Common issues:

    • Invalid or missing API authentication token may cause authentication failures.
    • Incorrect instance name can lead to errors indicating the instance does not exist.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Authentication errors: Verify that the API key credential is correctly set up and valid.
    • Instance not found: Confirm the instance name is correct and exists in the Evolution platform.
    • JSON parsing errors: Ensure input JSON properties (if any) are well-formed.

  • To resolve errors, check credentials, validate input parameters, and ensure network connectivity.

Links and References

Discussion