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 in scenarios where you need to retrieve user or business profile data programmatically, such as integrating contact profiles into workflows, automating customer support, or enriching CRM records.
Example use cases:
- Fetching a WhatsApp contact's profile information by their number.
- Retrieving business profile details from an external system using the instance name.
- Automating profile lookups before sending personalized messages.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to query against. This identifies the specific environment or account within the Evolution API. |
| Contato | The contact number (remoteJid) whose profile is to be fetched. |
Output
The node outputs a JSON array containing the profile data retrieved from the Evolution API. Each item in the output array corresponds to the profile information of the requested contact, including fields returned by the API such as name, status, profile picture URL, or other profile metadata.
If the API supports binary data (e.g., profile pictures), it would be included accordingly, but this is not explicitly shown in the source code.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is set to
https://doc.evolution-api.com/api-reference. - Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the operation is not supported. Ensure that the resource is "profile-api" and the operation is one of the supported ones like "fetch-profile".
- Missing required parameters: Both "Nome Da Instância" and "Contato" are required. Omitting these will likely cause the API call to fail.
- API authentication errors: Make sure the API key or token is correctly configured and valid.
- Network or API errors: Check connectivity and API availability if requests fail.
Links and References
- Evolution API Documentation (base URL used in the node)
- n8n documentation on creating custom nodes