Actions11
Overview
The Quepasa (Whatsapp) node's "Webhook" resource with the "Find" operation is designed to interact with a non-official WhatsApp API, specifically for managing or querying webhooks. This node allows users to search for existing webhook configurations associated with their WhatsApp bot.
Common scenarios:
- Retrieving a list of all configured webhooks for a WhatsApp bot.
- Auditing or verifying webhook endpoints currently set up in your Quepasa WhatsApp integration.
- Automating monitoring or management tasks related to webhook subscriptions.
Practical example:
A user wants to check which URLs are currently registered as webhooks for their WhatsApp bot to ensure messages and events are being delivered to the correct endpoints.
Properties
| Display Name | Type | Meaning |
|---|---|---|
| Authentication | options | Selects how credentials are provided: either by entering parameters manually or using predefined Quepasa credentials. |
| BaseUrl | string | The base URL of the Quepasa API. Required if using manual parameter authentication. |
| Token | string | The token for the WhatsApp bot. Used to authenticate API requests when not using predefined credentials. |
Note:
- BaseUrl and Token are only required if "Authentication" is set to "Parameters".
- When "Predefined Quepasa Credentials" is selected, these values are taken from n8n credentials.
Output
The output is a JSON array containing information about the found webhooks. Each item typically includes details such as:
[
{
"id": "string", // Unique identifier of the webhook
"url": "string", // Webhook endpoint URL
"event": "string", // Event type the webhook listens to
"status": "string", // Status of the webhook (e.g., active/inactive)
// ...other fields depending on API response
}
]
Note:
- The exact structure may vary based on the Quepasa API's response.
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to the Quepasa (non-official WhatsApp) API.
- API Key/Token: A valid WhatsApp bot token is required.
- n8n Credentials: If using "Predefined Quepasa Credentials", you must configure them in n8n under the appropriate credential type.
- Environment: Ensure network access to the specified BaseUrl.
Troubleshooting
Common issues:
- Invalid Token or BaseUrl:
- Error message: "Authentication failed" or similar.
Resolution: Double-check the token and BaseUrl. If using predefined credentials, verify they are correctly set up in n8n.
- Error message: "Authentication failed" or similar.
- Network Errors:
- Error message: "ENOTFOUND", "ECONNREFUSED", etc.
Resolution: Ensure the BaseUrl is reachable from your n8n instance.
- Error message: "ENOTFOUND", "ECONNREFUSED", etc.
- Insufficient Permissions:
- Error message: "403 Forbidden" or "401 Unauthorized".
Resolution: Make sure the token has the necessary permissions to access webhook resources.
- Error message: "403 Forbidden" or "401 Unauthorized".
- Unexpected API Response:
- Error message: "Cannot read property 'body' of undefined" or similar.
Resolution: Check that the Quepasa API is operational and returning expected data.
- Error message: "Cannot read property 'body' of undefined" or similar.
