Evolution API icon

Evolution API

Interact with Evolution API

Overview

This node, named "Evolution API," is designed to interact with the Evolution API service. It supports multiple resources and operations, including the "Perfil" resource with the "Buscar Perfil Profissional" operation. The node fetches professional profile information based on provided input parameters such as instance name and contact number.

Common scenarios for this node include:

  • Retrieving detailed professional profile data from an external system identified by an instance name.
  • Automating workflows that require fetching user or business profiles by contact number.
  • Integrating profile data into other systems or processes within n8n.

For example, a user might use this node to fetch a professional profile by specifying the instance of the Evolution API they want to query and the contact number of the professional whose profile they want to retrieve.

Properties

Name Meaning
Nome Da Instância The name of the Evolution API instance to connect to.
Contato The contact number (remoteJid) used to identify the professional profile to be fetched.

Output

The node outputs a JSON array containing the data returned by the Evolution API for the requested professional profile. Each item in the array corresponds to one profile record retrieved.

If the API returns binary data (not indicated in the provided code), it would typically be included in the output's binary property, but this node appears focused on JSON data only.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API service.
  • The node expects the Evolution API endpoint to be accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Operation Not Supported Error: If you select an unsupported operation for a given resource, the node throws an error stating the operation is not supported. Ensure you choose valid combinations of resource and operation.
  • Missing Required Parameters: Both "Nome Da Instância" and "Contato" are required. Omitting these will likely cause errors or empty responses.
  • API Authentication Issues: Incorrect or missing API credentials will prevent successful requests.
  • Network or Endpoint Errors: Ensure the Evolution API instance is reachable from your n8n environment.

Links and References

  • No direct links provided in the source code. For more details, consult the official Evolution API documentation or your internal API reference materials.

Discussion