Evolution API

Overview

This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the provided Resource "Instance" and Operation "Connect Instance," it enables connecting to a specified instance by its name. This is useful in scenarios where you need to programmatically establish connections to different instances managed via the Evolution API, such as automating workflows that depend on instance-specific data or actions.

Practical examples include:

• Automating the connection setup to an instance before performing further operations.
• Integrating instance management into larger automation pipelines.
• Dynamically selecting and connecting to instances based on workflow inputs.

Properties

Output

The node outputs a JSON array containing the result of the "Connect Instance" operation. The exact structure depends on the Evolution API's response but generally includes details about the connected instance, such as its status, identifiers, or metadata confirming the connection.

If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON-based.

Dependencies

• Requires an API key credential for authenticating with the Evolution API.
• The base URL for requests is set to https://doc.evolution-api.com/api-reference.
• The node expects JSON responses and sends JSON content-type headers.
• No additional environment variables or external services are explicitly required beyond the API authentication.

Troubleshooting

• Unsupported operation error: If the node throws an error stating the operation is unsupported, verify that the Resource and Operation names are correctly set and supported by the node.
• Authentication errors: Ensure that a valid API key credential is configured in n8n for the Evolution API.
• Instance not found: If the specified instance name does not exist or is misspelled, the API may return an error or empty response. Double-check the instance name input.
• Network issues: Connectivity problems to the Evolution API endpoint can cause failures; ensure network access and correct base URL configuration.

Links and References

• Evolution API Documentation (as referenced in the node's base URL)