Actions11
Overview
The Quepasa (Whatsapp) node's "Control" resource with the "Get Picture" operation allows you to retrieve a profile or group picture from a WhatsApp chat, group, or user. This can be useful for automating workflows that require fetching and processing WhatsApp images, such as archiving group pictures, displaying user avatars in dashboards, or triggering actions based on profile image changes.
Example scenarios:
- Downloading and storing WhatsApp group pictures for compliance or archival.
- Displaying contact or group images in custom CRM or notification systems.
- Monitoring for changes in group pictures and triggering alerts.
Properties
| Display Name | Type | Description |
|---|---|---|
| Authentication | options | Select how to authenticate: via direct parameters or predefined credentials. |
| BaseUrl | string | The base URL of the Quepasa API (required if using parameter authentication). |
| Token | string | The WhatsApp bot token (required if using parameter authentication). |
| Chat ID | string | The target conversation, group, or E164 phone number whose picture you want to fetch. |
| Picture ID | string | (Optional) Used to check for updates or cache validation of the picture. |
| Download Binary | boolean | If enabled, returns the picture as binary data instead of JSON metadata. |
| Binary Property | string | Name of the binary property to store the file (required if Download Binary is true). |
| File Name | string | Optional file name and extension for the downloaded picture (auto-generated if left blank). |
Output
If "Download Binary" is false:
The output will be a JSON object containing metadata about the picture, such as its URL, ID, or other relevant information provided by the Quepasa API.If "Download Binary" is true:
The output will include a binary property (with the specified name) containing the actual image file data. Additional fields may include file name and MIME type.
Example JSON output (when not downloading binary):
{
"pictureId": "1234567890",
"url": "https://api.quepasa.org:31000/pictures/1234567890",
"chatid": "441234567890@c.us"
}
Binary output:
A binary field (e.g., data) will contain the image file, suitable for use in subsequent n8n nodes that process files.
Dependencies
- External Service: Requires access to the Quepasa (WhatsApp) API endpoint.
- Authentication: Either direct token and base URL, or pre-configured n8n credentials (
quepasaTokenAuthApi). - n8n Configuration: If using predefined credentials, ensure they are set up in n8n’s credential manager.
Troubleshooting
Invalid Credentials:
Error messages like "Authentication failed" indicate incorrect token or base URL. Double-check your credentials and API endpoint.Missing Required Fields:
Errors about missing "Chat ID" or "Token" mean required properties were not provided. Ensure all mandatory fields are filled.Picture Not Found:
If the specified Chat ID does not exist or has no picture, the API may return an error or empty result.Binary Output Issues:
If "Download Binary" is enabled but "Binary Property" is not set, the node may throw a configuration error.API Connectivity:
Network errors or timeouts suggest issues reaching the Quepasa API. Check your network/firewall settings.