Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group 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 of a specified contact from an Evolution API instance. This is useful in scenarios where you need to retrieve detailed profile data (such as user or business profiles) programmatically within an n8n workflow.
Practical examples include:
- Automatically retrieving contact profile details when processing messages or events.
- Enriching customer data by fetching up-to-date profile information from an external system.
- Integrating profile data retrieval into automated communication or CRM workflows.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Contact | The contact number (remote JID) whose profile is to be fetched. |
Output
The node outputs a JSON array containing the profile data retrieved from the Evolution API for the specified contact. The structure of the JSON depends on the API response but generally includes profile details such as contact identifiers, names, status, and possibly business or professional profile information.
If the API supports binary data (e.g., profile pictures), this would typically be included in the output's binary field, but based on the provided code and properties, the focus is on JSON profile data.
Dependencies
- Requires an active Evolution API credential configured in n8n to authenticate requests.
- Depends on the Evolution API service being accessible at its base URL (
https://doc.evolution-api.com/api-reference). - The node uses internal helper functions mapped by resource and operation to execute the correct API call.
Troubleshooting
- Unsupported operation error: If the node throws an error stating the operation is unsupported, verify that the selected resource and operation are valid and implemented.
- Missing or invalid credentials: Ensure the API key or authentication token for the Evolution API is correctly set up in n8n.
- Invalid instance name or contact: Double-check that the instance name and contact number are correctly entered and correspond to existing entities in the Evolution API.
- Network or API errors: Check network connectivity and API availability; also review API rate limits or permission issues.
Links and References
- Evolution API official documentation: https://doc.evolution-api.com/api-reference
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/