Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node "Evolution API" allows users to interact with the Evolution API service. Specifically, for the Resource "Profile" and Operation "Buscar Perfil" (Fetch Profile), it fetches profile information of a contact based on the provided instance name and contact number. This node is useful in scenarios where you need to retrieve detailed 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:
- Automatically fetching user profile details when a new contact is added.
- Enriching CRM records with up-to-date profile information.
- Validating contact existence and retrieving metadata before sending messages.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Contact | The contact number (remoteJid) whose profile is to be fetched. |
Output
The node outputs an array of JSON objects representing the profile data retrieved from the Evolution API for the specified contact. Each object contains the profile details as returned by the API, which may include fields such as contact identifiers, display names, profile pictures, status messages, and other metadata related to the contact's profile.
If the API supports binary data (e.g., profile images), the node would handle this accordingly, but based on the provided code and properties, the output focuses on JSON profile information.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n to authorize requests to the Evolution API.
- The base URL for API requests is set to
https://doc.evolution-api.com/api-reference. - Proper configuration of the "Instance Name" property to target the correct Evolution API instance.
Troubleshooting
- Operation not supported error: If the node throws an error stating that the operation is not supported, verify that the resource and operation names are correctly set to "profile-api" and "fetch-profile" respectively.
- Authentication errors: Ensure that the API key or authentication token is correctly configured in the node credentials.
- Empty or missing profile data: Confirm that the contact number is valid and exists in the Evolution API system.
- Network issues: Check connectivity to the Evolution API endpoint and ensure no firewall or proxy is blocking requests.
Links and References
- Evolution API Documentation (base URL used in the node)
- n8n documentation on Creating Custom Nodes