Actions10
- Message Actions
- Webhook Actions
- Control Actions
Overview
The Quepasa (Whatsapp) node's "Control" resource with the "Get Picture" operation allows you to retrieve the profile picture of a WhatsApp chat, group, or user by specifying their Chat ID. This can be useful for automating processes that require fetching and storing contact or group images, such as syncing WhatsApp data with CRM systems, archiving group information, or displaying avatars in dashboards.
Practical examples:
- Downloading and saving WhatsApp group pictures for team directories.
- Displaying user or group avatars in custom applications.
- Checking if a group's picture has changed by using the Picture ID for cache validation.
Properties
| Name | Type | Meaning |
|---|---|---|
| Authentication | options | Selects how to authenticate: via direct parameters or predefined Quepasa 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 identifier of the chat, group, or E164 phone number whose picture is being fetched. |
| Picture ID | string | Optional. Used to check for updates or cache validation of the picture. |
| Download Binary | boolean | If true, returns the picture as binary data; otherwise, returns metadata as JSON. |
| Binary Property | string | Required if Download Binary is true. The property name under which the binary data is stored. |
| 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 is a JSON object containing metadata about the picture. Typical fields may include:chatId: The ID of the chat/group/user.pictureId: The unique identifier of the picture.urlor similar: A link to the picture or related metadata.
If "Download Binary" is true:
The output includes a binary property (with the specified name) containing the image file. Additional JSON fields may provide context such aschatId,filename, etc.
Dependencies
- External Service: Requires access to the Quepasa (Unofficial WhatsApp) API.
- Authentication: Either direct parameters (BaseUrl and Token) or predefined n8n credentials (
quepasaTokenAuthApi). - n8n Configuration: If using predefined credentials, ensure they are set up in n8n’s credential store.
Troubleshooting
Common Issues:
- Invalid Credentials: If the BaseUrl or Token is incorrect, authentication will fail.
- Missing Required Fields: Not providing Chat ID or required authentication details will result in errors.
- Binary Output Misconfiguration: If "Download Binary" is enabled but "Binary Property" is not set, the node may throw an error.
- Picture Not Found: If the Chat ID does not correspond to a valid WhatsApp entity, the API may return an error or empty result.
Error Messages:
"Authentication failed": Check your BaseUrl and Token or verify your n8n credentials."Chat ID not found": Ensure the Chat ID is correct and exists in WhatsApp."Missing required property": Make sure all required fields are filled, especially when toggling binary output.