Quepasa (Whatsapp) icon

Quepasa (Whatsapp)

Non Official Whatsapp API

Actions11

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 particularly useful for workflows where you need to retrieve and process files or media (such as images, documents, or audio) that were sent or received via WhatsApp.

Common scenarios:

  • Automatically saving incoming WhatsApp attachments to cloud storage.
  • Processing received documents or images in subsequent workflow steps.
  • Archiving WhatsApp media for compliance or record-keeping.

Example:
A customer sends a PDF invoice via WhatsApp. This node downloads the file, which can then be forwarded to an accounting system or stored in a document management platform.

Properties

Display Name Type Description
Authentication options Select how to provide credentials: "Parameters" (manual entry) or "Predefined Quepasa Credentials".
BaseUrl string The base URL of your Quepasa API instance. Required if using "Parameters" authentication.
Token string The token for your WhatsApp bot. Required if using "Parameters" authentication.
Message ID string 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 available in output.
File Name string (Optional) The filename to assign to the downloaded file in the output.

Output

  • Binary Data:
    The node outputs a binary property (default name: data, or as specified in "Binary Property") containing the downloaded file from the WhatsApp message.
  • File Name:
    If provided, the output binary data will have the specified file name.
  • JSON Output:
    The JSON part of the output may include metadata about the operation or error messages if something goes wrong.

Example Output Structure:

{
  "json": {
    // Any additional metadata or empty object
  },
  "binary": {
    "data": {
      "data": "<base64-encoded file content>",
      "fileName": "downloaded.pdf",
      "mimeType": "application/pdf"
    }
  }
}

Note: The actual property name under binary depends on your "Binary Property" input.

Dependencies

  • External Service: Requires access to a running Quepasa API instance.
  • Authentication:
    • Either manual entry of BaseUrl and Token, or use of 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:
    • Error: "Authentication failed" or similar.
      • Ensure the BaseUrl and Token are correct, or that the selected credential is valid.
  • Message Not Found:
    • Error: "Message not found" or HTTP 404.
      • Double-check the Message ID.
  • No Binary Output:
    • If the specified message does not contain downloadable content, the binary property may be missing or empty.
  • Incorrect Binary Property Name:
    • If you specify a custom binary property name, make sure to reference it correctly in downstream nodes.

Error Handling:

  • If "Continue On Fail" is enabled, errors will be included in the output JSON with an error field.

Links and References

Discussion