Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The node named "Evolution API" is designed to interact with the Evolution API service. It allows users to perform various operations on different resources exposed by the Evolution API. This node is useful for automating workflows that require integration with Evolution API endpoints, such as data retrieval, creation, update, or deletion of entities managed by the API.

Typical use cases include:

  • Automating data synchronization between Evolution API and other systems.
  • Triggering actions in Evolution API based on events in n8n workflows.
  • Managing resources programmatically without manual API calls.

For example, a user might configure this node to fetch records from a specific resource in Evolution API, process them within n8n, and then update or create related entries in another system.

Properties

Name Meaning
resource The type of resource in Evolution API you want to work with (e.g., users, orders).
operation The action to perform on the selected resource (e.g., get, create, update, delete).

Note: The exact list of resources and operations is defined externally in the resourceOperationsFunctions mapping, which links resource-operation pairs to their implementation functions.

Output

The node outputs an array of JSON objects representing the result of the executed API operation. Each item in the output corresponds to a processed entity or response returned by the Evolution API.

  • The output is structured as JSON data.
  • There is no indication that the node handles binary data.

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 the Evolution API to respond with JSON-formatted data.
  • No additional external dependencies are indicated.

Troubleshooting

  • Unsupported Operation Error: If the user selects an operation not supported for the chosen resource, the node throws an error stating the operation is not supported. To fix this, ensure the operation-resource combination is valid and implemented.
  • API Authentication Issues: Since the node requires credentials, missing or invalid API keys will cause authentication failures. Verify that the correct API key is configured.
  • Network or Endpoint Errors: Connectivity issues or incorrect base URLs can cause request failures. Confirm the base URL and network access.
  • Unexpected Response Format: The node expects JSON responses; if the API returns non-JSON or malformed data, processing may fail.

Links and References

Discussion