Actions11
Overview
The Quepasa (Whatsapp) node for n8n enables sending messages via the unofficial Quepasa WhatsApp API. Specifically, with the Message resource and Send operation, this node allows you to send various types of messages—including text, attachments (via base64, binary, or URL), and more—to WhatsApp users, groups, or chats. This is useful for automating notifications, alerts, customer support responses, or any workflow requiring WhatsApp communication.
Example scenarios:
- Sending automated order confirmations to customers on WhatsApp.
- Delivering files (PDFs, images) to a group chat.
- Notifying a user with a custom message and attachment when a workflow event occurs.
Properties
Below are the input properties relevant to the Message resource and Send operation:
| Display Name | Type | Description |
|---|---|---|
| Authentication | options | Choose between entering parameters manually or using predefined Quepasa credentials. |
| BaseUrl | string | The base URL of the Quepasa API (required if using manual parameters). |
| Token | string | The WhatsApp bot token (required if using manual parameters). |
| Message ID | string | (Optional) Identifier for the message, used for status checks, revoking, or editing after sending. |
| Method | options | Select how to send the message: - Send Any - Send Attachment Base64 - Send Attachment Binary - Send Attachment By Url - Send Text |
| Binary Property | string | (Required for "Send Attachment Binary") Name of the binary property containing file data. |
| Text | string | The text content of the message (used in most methods except pure binary). |
| Chat ID | string | (Required) Destination chat/group/phone number (E164 format). |
| BASE64 Content | string | Base64-encoded file content (required for "Send Attachment Base64"; optional for "Send Any"). |
| Url | string | URL to an attachment (required for "Send Attachment By Url"; optional for "Send Any"). |
| File Name | string | (Optional) Name and extension for the file; auto-generated if not provided. |
| MIME | string | (Optional) MIME type of the attachment (e.g., application/pdf). |
| File Length | number | (Optional) Size of the file in bytes. |
| Track ID | string | (Optional) System identifier to avoid duplicate messages. |
| In Reply To | string | (Optional) Message ID to reply to. |
Note: Some fields appear only for specific methods. For example, "Binary Property" is required only for "Send Attachment Binary".
Output
The output is a JSON object (or array of objects) representing the result of the message send operation. While the exact structure depends on the Quepasa API response, typical fields may include:
{
"messageId": "string", // Unique identifier for the sent message
"status": "string", // Status of the message (e.g., "sent", "queued")
"chatId": "string", // Destination chat/group/phone number
"timestamp": "number", // Time the message was sent
"details": { ... } // Additional details as returned by the API
}
If the method involves sending binary data, the node can also output binary fields, typically reflecting the file sent or received.
In case of errors (and if "Continue On Fail" is enabled), the output may contain an error field with the error message.
Dependencies
- External Service: Requires access to the Quepasa WhatsApp API endpoint.
- API Credentials: Either manual entry (BaseUrl + 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:
- Authentication Errors: Invalid or missing token/base URL will prevent successful API calls. Double-check your credentials.
- Invalid Chat ID: Ensure the Chat ID is correct and in E164 format for phone numbers.
- Missing Required Fields: Depending on the selected method, some fields (like "Binary Property" or "BASE64 Content") are mandatory.
- File Upload Problems: For binary or base64 uploads, ensure the file data is correctly encoded and referenced.
Error Messages:
"Authentication failed": Check your token and base URL."Missing required parameter: <field>": Ensure all required fields for the chosen method are filled."Invalid chat ID": Verify the destination identifier."File not found in binary property": Make sure the specified binary property exists in the input.