Actions10
- Message Actions
- Webhook Actions
- Control Actions
Overview
The Quepasa (Whatsapp) node's "Webhook" resource with the "Remove" operation is designed to remove or unregister a webhook URL from the Quepasa WhatsApp API. This is useful when you want to stop receiving event notifications at a specific endpoint, for example, when decommissioning an integration or changing your webhook infrastructure.
Common scenarios:
- Disabling event delivery to a previously registered webhook.
- Cleaning up unused webhooks to maintain security and reduce unnecessary traffic.
- Rotating webhook URLs as part of maintenance or migration.
Practical example:
You have set up a webhook to receive incoming WhatsApp messages in your CRM. If you change your CRM or no longer need this integration, you can use this node to remove the old webhook registration from Quepasa.
Properties
| 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. |
| Url | string | The webhook URL to be removed/unregistered from Quepasa. |
Output
The output will be a JSON object (or array) reflecting the result of the webhook removal operation. Typical fields may include:
successorstatus: Indicates whether the webhook was successfully removed.message: Additional information about the operation outcome.error: If the operation failed, this field may contain the error message.
Example output:
[
{
"status": "success",
"message": "Webhook removed"
}
]
Or, in case of failure:
[
{
"error": "Webhook not found"
}
]
Dependencies
- External Service: Requires access to the Quepasa WhatsApp API.
- API Credentials: Either a manually provided BaseUrl and Token, or a configured n8n credential of type
quepasaTokenAuthApi. - n8n Configuration: If using predefined credentials, ensure they are set up in n8n under the appropriate credential type.
Troubleshooting
Common issues:
- Invalid credentials: If the BaseUrl or Token is incorrect, the node will fail to authenticate.
- Webhook not found: Attempting to remove a webhook that does not exist will result in an error message.
- Network errors: Connectivity issues between n8n and the Quepasa API endpoint can cause failures.
Error messages and resolutions:
"Authentication failed": Check your BaseUrl and Token, or verify your n8n credentials."Webhook not found": Ensure the URL you are trying to remove matches exactly with the one registered."Network error": Verify network connectivity and firewall settings.