Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node named "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the resource Chat and operation Fetch Profile Picture, it allows users to retrieve the profile picture of a specified contact from a given instance. This is useful in scenarios where you want to programmatically access user profile images for contacts within a chat system, such as displaying avatars in a custom dashboard or syncing contact images.
Practical examples include:
- Fetching and displaying profile pictures of contacts in a CRM integrated with chat.
- Automating the update of contact images in external systems based on chat data.
- Archiving or backing up profile pictures for compliance or record-keeping.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the chat 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 fetch profile picture operation. The exact structure depends on the Evolution API response but typically includes metadata about the contact and the profile picture URL or binary data reference.
If the profile picture is returned as binary data, it will be accessible in the node's binary output under the binary property, allowing further processing or saving of the image file.
Dependencies
- Requires an API key credential for authenticating with the Evolution API service.
- The node expects the Evolution API base URL and headers to be configured internally.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Unsupported operation error: If you select an operation not supported by the node, it will throw an error indicating the function is unsupported. Ensure you use only valid resource-operation combinations.
- Missing or invalid credentials: The node requires a valid API key credential; missing or incorrect credentials will cause authentication failures.
- Invalid contact number format: The contact number must be provided in the correct international format (e.g., country code + number) to successfully fetch the profile picture.
- Network or API errors: Connectivity issues or API downtime may cause request failures. Check network connectivity and Evolution API status.
Links and References
- Evolution API Documentation (base URL referenced in the node)
- n8n documentation on Creating Custom Nodes