Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node, named "Evolution API," is designed to interact with the Evolution API service. Specifically, for the resource Perfil and operation Buscar Perfil Profissional, it fetches professional profile information based on a given contact number and instance name. This can be useful in scenarios where you need to retrieve detailed professional profile data from an external system by providing identifiers such as the instance name and contact number.
Practical examples include:
- Retrieving a professional's profile details in a CRM workflow.
- Enriching contact records with professional profile data during lead processing.
- Automating profile lookups in customer support or sales automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to query against. This identifies which instance of the service to use. |
| Contato | The contact number (remoteJid) whose professional profile is to be fetched. |
Output
The node outputs a JSON array containing the fetched professional profile data corresponding to the provided contact number and instance name. Each item in the output array represents the profile information retrieved from the Evolution API.
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 service.
- The base URL for requests is set to
https://doc.evolution-api.com/api-reference. - The node expects the user to configure credentials that provide access to the Evolution API.
- No other external dependencies are explicitly mentioned.
Troubleshooting
- Operation Not Supported Error: If you select an unsupported operation for a 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 fields. Omitting these will likely cause errors or empty results.
- API Authentication Issues: If the API key or credentials are invalid or missing, the node will fail to authenticate with the Evolution API.
- Network or Endpoint Errors: Since the base URL is fixed, network issues or changes in the API endpoint may cause failures.
To resolve these issues:
- Verify that the resource and operation selected are supported.
- Provide all required input parameters.
- Check that the API key credential is correctly configured and valid.
- Confirm network connectivity and API availability.
Links and References
- Evolution API Documentation (base URL referenced in the node)
- n8n Documentation on Creating Custom Nodes