Actions10
- Message Actions
- Webhook Actions
- Control Actions
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. In this context, the "Find" operation likely retrieves information about existing webhook configurations associated with your WhatsApp bot.
Common scenarios:
- Listing all registered webhooks for a WhatsApp bot.
- Auditing or verifying current webhook endpoints.
- Integrating with other systems that need to know which webhooks are active.
Practical example:
You might use this node in an n8n workflow to fetch and display all webhook URLs currently set up for your WhatsApp integration, perhaps before updating or deleting them.
Properties
| Name | Type | Meaning |
|---|---|---|
| Authentication | options | Selects how credentials are provided: either manually ("Parameters") or via predefined Quepasa 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. |
Output
The output will be a JSON array containing information about the webhooks found. Each item in the array represents a webhook configuration and typically includes fields such as:
- Webhook URL
- Event types subscribed
- Status or metadata
Note: The exact structure depends on the Quepasa API response for the webhook "find" operation, but you can expect standard webhook details.
Dependencies
- External Service: Requires access to the Quepasa (WhatsApp) API.
- API Credentials: You must provide either:
- A BaseUrl and Token (manual entry), or
- Predefined Quepasa credentials configured in n8n.
- n8n Configuration: If using predefined credentials, ensure they are set up under n8n’s credentials section.
Troubleshooting
Common issues:
- Invalid Credentials: If the BaseUrl or Token is incorrect, authentication will fail. Double-check your values.
- Network Errors: Ensure n8n can reach the Quepasa API endpoint (check firewalls, VPNs, etc.).
- Missing Permissions: The token used must have permission to list webhooks.
Error messages:
"Authentication failed": Check your BaseUrl and Token or update your predefined credentials."Resource not found": The specified webhook resource may not exist; verify your setup."Request failed with status code XXX": Indicates an HTTP error from the API; check the API documentation for meaning.