Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração 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 when you need to retrieve user or business profile data programmatically from the Evolution API, such as obtaining contact details or verifying profile information in automation workflows.
Practical examples include:
- Fetching a user's profile by their contact number to personalize communication.
- Retrieving business profile information for CRM enrichment.
- Automating profile lookups during customer support processes.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to target within the Evolution API environment. |
| Contato | The contact number (remoteJid) whose profile information you want to fetch. |
Output
The node outputs an array of JSON objects representing the fetched profile data. Each object contains the profile details retrieved from the Evolution API corresponding to the specified contact and instance. The exact structure depends on the API response but generally includes fields like contact identifiers, profile names, and possibly business-related information.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API endpoint to be accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Operation not supported error: If you select an unsupported operation-resource combination, the node throws an error indicating the operation is not supported. Ensure you use valid combinations like "Perfil" with "Buscar Perfil".
- Missing required properties: Both "Nome Da Instância" and "Contato" are mandatory. Omitting them will likely cause errors or empty results.
- API authentication issues: Invalid or missing API credentials will prevent successful requests. Verify that the API key or token is correctly configured.
- Network or API errors: Connectivity problems or API downtime can cause failures. Check network access and Evolution API status.
Links and References
- Evolution API official documentation (not provided in source; consult your API provider)
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/