Actions10
- Message Actions
- Webhook Actions
- Control Actions
Overview
The Quepasa (Whatsapp) - Message: Download node allows you to download the binary content of a specific WhatsApp message using the Quepasa API. This is useful for workflows where you need to retrieve files or media (such as images, documents, or audio) that were sent or received via WhatsApp and process them further in n8n.
Common scenarios:
- Automatically saving attachments from WhatsApp messages to cloud storage.
- Processing incoming media files for analysis or archiving.
- Forwarding downloaded files to other services or users.
Example:
A business receives invoices as PDF files via WhatsApp. This node can be used to fetch those PDFs and upload them to an accounting system.
Properties
| Name | Type | Meaning |
|---|---|---|
| Authentication | options | Selects how to authenticate with the Quepasa API: either by entering parameters manually or using predefined credentials. |
| BaseUrl | string | The base URL of the Quepasa API. Required if using manual parameter authentication. |
| Token | string | The token for the WhatsApp bot. Required if using manual parameter authentication. |
| Message ID | string | The unique identifier of the WhatsApp message whose content you want to download. |
| Binary Property | string | The name of the binary property under which the downloaded file will be stored in the output. |
| File Name | string | (Optional) The filename to assign to the downloaded file in the output. |
Output
- Binary Data:
The node outputs the downloaded file as binary data under the property name specified in "Binary Property".- The binary field contains the file's contents, and may include metadata such as the filename (if provided).
- The
jsonpart of the output may contain additional information about the message or the download operation.
Example output structure:
{
"json": {
// Additional info or empty
},
"binary": {
"data": {
"data": "<base64-encoded file content>",
"fileName": "downloaded.pdf",
"mimeType": "application/pdf"
}
}
}
(The actual property name under "binary" depends on your "Binary Property" input.)
Dependencies
- Quepasa API: Requires access to a running Quepasa (WhatsApp) API instance.
- Authentication: Either manual entry of BaseUrl and Token, or use of predefined Quepasa credentials configured in n8n.
- n8n Configuration: If using predefined credentials, ensure they are set up in n8n’s credential store.
Troubleshooting
Invalid Credentials:
Error:Authentication failedor similar.
Solution: Double-check your BaseUrl and Token, or verify your predefined credentials in n8n.Message Not Found:
Error:Message not foundor similar.
Solution: Ensure the Message ID is correct and the message exists in Quepasa.No Binary Output:
Error: Output does not contain expected binary data.
Solution: Verify that the message actually contains downloadable content and that the "Binary Property" name matches your workflow expectations.File Name Issues:
If "File Name" is left blank, the output may have a generic or missing filename. Specify it if needed for downstream nodes.