Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo 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" (Fetch Professional Profile), it retrieves professional profile information based on a given contact number and instance name. This node is useful in scenarios where you need to programmatically fetch detailed professional profile data from the Evolution API, such as integrating contact management systems, CRMs, or automating user profile lookups.
Practical examples include:
- Automatically retrieving professional profiles of contacts when processing incoming messages.
- Enriching customer data by fetching up-to-date professional details.
- Integrating with other workflows that require professional profile verification or display.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to connect to within the Evolution API environment. |
| Contato | The contact number (remote JID) for which the professional profile will be fetched. |
Output
The node outputs an array of JSON objects representing the fetched professional profile(s). Each object contains the profile data returned by the Evolution API for the specified contact. The exact structure depends on the API response but typically includes fields related to the professional's identity, contact details, and possibly business-related information.
If the node supports binary data output, it would represent associated media or documents linked to the profile, but this is not indicated in the provided code.
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 external dependencies are indicated beyond the standard n8n workflow environment.
Troubleshooting
- Operation Not Supported Error: If you select an unsupported operation or resource, the node throws an error stating the operation is not supported. Ensure that the resource is set to "Perfil" and the operation to "Buscar Perfil Profissional".
- Missing Required Parameters: Both "Nome Da Instância" and "Contato" are required. Omitting these will likely cause errors or empty responses.
- API Authentication Issues: Make sure the API key credential is correctly configured and has sufficient permissions.
- Network or API Errors: Check network connectivity and API availability if requests fail.
Links and References
- Evolution API official documentation (not provided here; consult your API provider)
- n8n documentation on creating custom nodes and using credentials: https://docs.n8n.io/
- General API integration best practices