Evolution API icon

Evolution API

Interact with Evolution API

Overview

The node named "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the resource "Instance" and operation "Disconnect Instance," it allows users to log out or disconnect a specified instance by its name. This is useful in scenarios where you need to programmatically terminate sessions or connections to instances managed via the Evolution API.

For example, if you have multiple instances running and want to ensure that a particular instance is logged out or disconnected before performing maintenance or redeployment, this node operation facilitates that action.

Properties

Name Meaning
Name Da Insticância The name of the instance you want to disconnect. You must provide the exact instance name.

Output

The node outputs a JSON array containing the result of the disconnect operation. The structure of the JSON output depends on the response from the Evolution API but generally will include confirmation of the logout/disconnect action or any relevant status messages.

No binary data output is indicated.

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.
  • Proper configuration of the API authentication credentials within n8n is necessary.

Troubleshooting

  • Operation Not Supported Error: If you receive an error stating the operation is not supported, verify that the resource and operation names are correctly set to "Instance" and "Disconnect Instance" respectively.
  • Authentication Errors: Ensure that the API key credential is valid and has sufficient permissions to perform logout operations.
  • Instance Not Found: If the specified instance name does not exist or is misspelled, the API may return an error or no effect. Double-check the instance name input.
  • Network Issues: Connectivity problems to the Evolution API endpoint can cause failures; verify network access and endpoint availability.

Links and References

Discussion