Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the resource Perfil and operation Buscar Perfil, it fetches profile information based on provided instance and contact details. This node is useful in scenarios where you need to retrieve user or business profile data from the Evolution API, such as integrating contact profiles into workflows, automating customer data retrieval, or enriching datasets with profile information.
Example use cases:
- Fetching a user's profile by their contact number to personalize communication.
- Retrieving business profile details for CRM updates.
- Automating profile lookups during support ticket creation.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to connect to within the Evolution API. |
| Contato | The contact number (remote JID) whose profile is to be fetched. |
Output
The node outputs an array of JSON objects representing the profile data retrieved from the Evolution API. Each object contains the profile details corresponding to the requested contact within the specified instance.
If the node supports binary data output, it would typically represent profile images or attachments; however, based on the provided code and properties, the output focuses on JSON profile information only.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- Needs proper configuration of the Evolution API credentials within n8n.
- The node depends on the Evolution API being accessible and responsive.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource combination, the node throws an error indicating the operation is not supported. Ensure that the resource is set to "Perfil" and the operation to "Buscar Perfil".
- Missing required parameters: Both "Nome Da Instância" and "Contato" are required. Omitting these will cause errors or empty results.
- Authentication failures: Verify that the API key credential is correctly configured and has necessary permissions.
- Network issues: Ensure the Evolution API endpoint is reachable from your environment.
Links and References
- Evolution API Documentation (Replace with actual URL)
- n8n documentation on Creating Custom Nodes