Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node named "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Chat resource and the Fetch Profile Picture operation, it allows users to retrieve the profile picture of a specified contact from a given instance.
This node is beneficial in scenarios where you want to programmatically access user profile images from a chat system integrated via the Evolution API. For example, it can be used in customer support workflows to display or log the profile pictures of contacts interacting through chat, or in marketing automation to personalize messages based on contact images.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Contact | The phone number of the contact whose profile picture you want to fetch (e.g., 5511999999999). |
Output
The node outputs a JSON array containing the result of the profile picture fetch operation. The exact structure depends on the Evolution API response but typically includes metadata about the contact and a link or data representing the profile picture.
If the profile picture is returned as binary data, it would be included accordingly, but based on the static code, the output is wrapped as JSON.
Dependencies
- Requires an API key credential for the Evolution API to authenticate requests.
- The node uses the base URL
https://doc.evolution-api.com/api-referencefor API calls. - Proper configuration of the Evolution API credentials within n8n is necessary.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node will throw an error indicating the function is not supported. Ensure that the resource is set to "chat-api" and the operation to "fetch-profile-picture".
- Missing required parameters: Both "Instance Name" and "Contact" are required. Omitting these will cause errors.
- API authentication issues: Make sure the API key credential is correctly configured and has sufficient permissions.
- Invalid contact number format: The contact number should follow the expected format (e.g., country code + number without spaces).
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on Creating Custom Nodes