Overview
The Quepasa Trigger node for n8n starts workflows when events are received from the Quepasa API via webhooks. It is typically used to automate processes in response to WhatsApp bot events, such as receiving new messages or notifications from the Quepasa platform. Common scenarios include integrating WhatsApp bots with CRMs, ticketing systems, or automating responses and data collection.
Practical examples:
- Automatically logging incoming WhatsApp messages into a database.
- Triggering support workflows when customers send specific keywords.
- Forwarding WhatsApp event data to other services for analytics or notifications.
Properties
| Name | Type | Meaning |
|---|---|---|
| Authentication | options | Selects how to authenticate: using direct parameters or predefined credentials. |
| BaseUrl | string | The base URL of the Quepasa API (required if using parameter-based authentication). |
| Token | string | The token for the WhatsApp bot; overrides credentials (required for parameter auth). |
| Forward Internal | boolean | Whether to forward internal messages sent by the API. |
| Track ID | string | Optional system identifier to avoid processing duplicate messages (shown if forwarding internal messages). |
| Extra Attributes | fixedCollection | Additional key-value attributes to include with the webhook trigger. |
Output
The node outputs the full JSON body received from the Quepasa webhook request. The structure of this output depends on the event type sent by Quepasa, but it will always be accessible as a JSON object under the json field in n8n.
Example output:
{
"json": {
// All fields as received from the Quepasa webhook POST body
}
}
- If binary data is sent, it is not explicitly handled by this node; only JSON payloads are processed.
Dependencies
- External Service: Requires access to the Quepasa API and a valid WhatsApp bot token.
- API Key / Credentials: Either direct entry of BaseUrl and Token, or use of predefined Quepasa credentials in n8n.
- n8n Configuration: Webhook endpoint must be reachable by Quepasa servers (publicly accessible URL).
Troubleshooting
Common Issues:
- Webhook Not Triggering: Ensure your n8n instance is publicly accessible and the webhook URL is correctly registered with Quepasa.
- Authentication Errors: Double-check that the correct BaseUrl and Token are provided, or that the predefined credentials are set up properly in n8n.
- 403 Forbidden Error: This may occur if the request does not originate from Quepasa or is identified as a bot by user-agent checks.
- Duplicate Messages: Use the "Track ID" property to help prevent processing the same message multiple times.
Error Messages:
"invalid request": Indicates an issue with the webhook registration or deletion process. Check your API credentials and network connectivity."403 Forbidden": The request was blocked due to failing user-agent validation or authorization checks.