Actions11
Overview
The Quepasa (Whatsapp) node's Webhook → Setup operation allows you to programmatically register a webhook URL with the Quepasa WhatsApp API. This enables your n8n workflow to receive real-time events (such as incoming messages or status updates) from your WhatsApp bot via HTTP callbacks. Typical use cases include automating responses, logging conversations, or integrating WhatsApp events into other systems.
Example scenarios:
- Automatically trigger workflows when a new WhatsApp message is received.
- Forward WhatsApp events to external services for analytics or archiving.
- Set up custom event handling for specific WhatsApp bot activities.
Properties
Below are the input properties relevant to the Webhook → Setup operation:
| Display Name | Type | Meaning |
|---|---|---|
| Authentication | options | Select how to provide credentials: either manually ("Parameters") or using predefined ones. |
| BaseUrl | string | The base URL of the Quepasa API (required if "Parameters" authentication is selected). |
| Token | string | The WhatsApp bot token (required if "Parameters" authentication is selected). |
| Url | string | The webhook endpoint that will receive events from Quepasa. |
| Forward Internal | boolean | Whether to forward internal events (optional; default: true). |
| Track ID | string | Optional system identifier to avoid duplicated messages. |
| Extra Attributes | collection | Additional key-value pairs to include in the webhook setup request. |
Output
The output of this operation is a JSON object (or array of objects) representing the result of the webhook setup request. While the exact structure depends on the Quepasa API response, typical fields may include:
{
"success": true,
"message": "Webhook registered successfully",
"webhookId": "1234567890",
// ...other fields returned by the API
}
- If an error occurs, the output may contain an
errorfield with a descriptive message.
Dependencies
- External Service: Requires access to the Quepasa WhatsApp API.
- API Credentials: Either a manually provided BaseUrl and Token, or a configured credential in n8n.
- n8n Configuration: If using predefined credentials, ensure the corresponding credential type is set up in n8n.
Troubleshooting
Common issues:
- Invalid Credentials: If the BaseUrl or Token is incorrect, the node will return an authentication error.
- Missing Required Fields: Not providing required fields (e.g., Url) will result in validation errors.
- Duplicate Webhook: Using the same Track ID may cause the API to reject duplicate webhook registrations.
Error messages:
"Authentication failed": Check your BaseUrl and Token, or verify your n8n credentials."Webhook registration failed": Ensure the Url is reachable and correctly formatted."Duplicate track ID": Use a unique Track ID for each webhook setup.