Actions11
Overview
The Quepasa (Whatsapp) node's "Webhook: Clear" operation is designed to clear or remove webhook configurations from a Quepasa WhatsApp bot instance. This is useful when you want to stop receiving webhook events, reset the webhook endpoint, or reconfigure integrations with external systems.
Common scenarios:
- Disabling event notifications temporarily or permanently.
- Resetting webhooks before setting up new endpoints.
- Troubleshooting by clearing potentially misconfigured webhooks.
Practical example:
You have integrated your WhatsApp bot with an external CRM via webhooks. If you need to disconnect or change the integration, you can use this operation to clear the existing webhook configuration.
Properties
| Display Name | Type | Meaning |
|---|---|---|
| Authentication | options | Selects how to provide credentials: either manually ("Parameters") or via predefined credentials. |
| BaseUrl | string | The base URL of the Quepasa API. Required if using manual parameters. |
| Token | string | The authentication token for the WhatsApp bot. Required if using manual parameters. |
Note: "BaseUrl" and "Token" are only required when "Authentication" is set to "Parameters".
Output
The output will be a JSON object (or array) indicating the result of the webhook clear operation. Typical fields may include:
{
"success": true,
"message": "Webhook cleared successfully"
}
Or, in case of error:
{
"error": "Detailed error message"
}
- The structure may vary depending on the API response, but generally includes a success indicator and a message.
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to a running Quepasa WhatsApp API server.
- API Key/Token: You must provide a valid Token for authentication.
- n8n Credentials: Optionally, you can use predefined credentials configured in n8n as "Predefined Quepasa Credentials".
Troubleshooting
Common issues:
- Invalid Token: If the provided token is incorrect or expired, the operation will fail with an authentication error.
- Incorrect BaseUrl: If the BaseUrl does not point to a valid Quepasa API instance, you may receive connection errors.
- Insufficient Permissions: The token used must have permissions to manage webhooks.
Error messages:
"Authentication failed": Check your Token and BaseUrl."Webhook not found": There may be no webhook configured to clear."Network error": Ensure the Quepasa API server is reachable from your n8n instance.
How to resolve:
- Double-check your credentials and API endpoint.
- Ensure the Quepasa service is running and accessible.
- Use the "Predefined Quepasa Credentials" option if available and properly configured in n8n.