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 a customer sends a message to your WhatsApp bot.
- Forwarding WhatsApp events to other services or internal tools.
Properties
| Display Name | Type | Description |
|---|---|---|
| Authentication | options | Select how to authenticate: either by entering parameters manually or using predefined credentials. |
| BaseUrl | string | The base URL of the Quepasa API (required if using manual parameters). Example: https://api.quepasa.org:31000 |
| Token | string | The token for your WhatsApp bot (required if using manual parameters). This overrides credentials. |
| Forward Internal | boolean | Whether to forward internal messages sent by the API. |
| Track ID | string | (Optional) System identifier to avoid duplicated messages. Only shown if "Forward Internal" is enabled. |
| Extra Attributes | fixedCollection | Additional key-value attributes to include with the webhook. |
Output
The node outputs the JSON body received from the Quepasa webhook request. The structure of this output depends on the event sent by Quepasa, but it will always be an array of objects representing the webhook payload.
Example output:
[
{
// All fields as provided by the Quepasa webhook event
"event": "message",
"data": {
"from": "+1234567890",
"body": "Hello!",
// ...other fields
}
}
]
- If the webhook receives binary data, it is not processed; only JSON payloads are returned.
Dependencies
- External Service: Requires access to the Quepasa API.
- API Key/Token: You must provide a valid Quepasa API token, either directly or via n8n credentials.
- n8n Configuration: Ensure that your n8n instance is accessible from the internet so Quepasa can reach the webhook endpoint.
Troubleshooting
Common issues:
- Webhook not triggered: Make sure your n8n instance is publicly accessible and the webhook URL is correctly registered with Quepasa.
- Authentication errors: Double-check your BaseUrl and Token, or ensure your credentials are set up properly in n8n.
- 403 Forbidden error: If the webhook is called by a bot or non-Quepasa user-agent, the node will reject the request. Ensure requests originate from Quepasa.
- Duplicate messages: Use the "Track ID" property to help prevent processing the same event multiple times.
Error messages:
"invalid request": Indicates a problem with the webhook registration or deletion process. Check your API credentials and network connectivity."authorization error": The request did not come from a recognized source. Verify the user-agent and authentication method.