Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node "Evolution API" allows users to interact with the Evolution API service. Specifically, for the Resource "Profile" and Operation "Fetch Profile," it fetches profile information related to a specified contact within an instance. This is useful in scenarios where you need to retrieve detailed profile data of contacts programmatically, such as integrating contact management or CRM systems, automating customer support workflows, or enriching contact data in marketing automation.
For example, you might use this node to:
- Retrieve a user's profile details by providing their contact number.
- Automate fetching business or professional profiles linked to contacts.
- Integrate profile data into other systems for personalized communication.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name of the instance where the profile resides. This identifies the specific environment or account context. |
| Contato | The contact number (remoteJid) whose profile you want to fetch. |
Output
The node outputs a JSON array containing the fetched profile data for the specified contact. Each item in the array represents the profile information retrieved from the Evolution API, structured according to the API's response format. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API base URL and headers to be configured internally.
- No additional external dependencies are indicated beyond the API access.
Troubleshooting
- Operation Not Supported Error: If you select an unsupported operation for the resource, the node throws an error indicating the operation is not supported. Ensure that the operation "fetch-profile" is correctly selected for the "profile-api" resource.
- Missing Required Parameters: Both "Name Da Instância" and "Contato" are required fields. Omitting these will likely cause errors or empty responses.
- API Authentication Issues: Make sure the API key credential is valid and has the necessary permissions to access profile data.
- Network or API Errors: Check network connectivity and API availability if requests fail.
Links and References
- Evolution API Documentation (as referenced in the node's base URL)
- n8n Documentation on Creating Custom Nodes