Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The "Evolution API" node allows you to interact with the Evolution API, specifically for operations related to profiles. In the context of the Perfil (Profile) resource and the Buscar Perfil (Fetch Profile) operation, this node retrieves profile information for a specified contact within a given instance. This is useful in scenarios where you need to look up user or business profile details based on a contact number, such as automating CRM updates, verifying contact information, or enriching data workflows.
Practical Example:
You could use this node to automatically fetch and store WhatsApp profile information for new leads entering your sales pipeline.
Properties
| Display Name | Type | Description |
|---|---|---|
| Nome Da Instância | String | Digite o nome da instância (Enter the name of the instance). Required. |
| Contato | String | Número do contato (Contact number). Required. |
Output
- The output is a JSON object (or array of objects) containing the fetched profile information for the specified contact.
- The exact structure depends on the Evolution API's response for the profile fetch operation, but typically includes fields such as contact identifiers, profile names, and possibly additional metadata.
- No binary data is returned by this operation.
Dependencies
- External Service: Requires access to the Evolution API.
- API Key/Credentials: You must configure valid credentials for the "evolutionApi" in n8n.
- Environment: Ensure network access to
https://doc.evolution-api.com/api-reference.
Troubleshooting
- Common Issues:
- Missing or invalid credentials will prevent the node from connecting to the Evolution API.
- Providing an incorrect instance name or contact number may result in empty results or errors.
- Error Messages:
"Operação não suportada."— This means the selected operation is not supported for the chosen resource. Double-check that you have selected the correct resource and operation.- API-specific errors may be returned if the contact does not exist or if there are permission issues.