Actions148
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
Overview
The node integrates with the SparkBot WhatsApp API, enabling various operations related to WhatsApp messaging and management. Specifically, for the Webhooks resource and the Enable Webhook operation, it allows users to activate a webhook by its ID. This is useful in scenarios where you want to start receiving real-time event notifications from the SparkBot platform via webhooks, such as message delivery updates or incoming messages.
Practical examples include:
- Enabling a webhook after creating it to start receiving WhatsApp event callbacks.
- Reactivating a previously disabled webhook without recreating it.
- Managing webhook lifecycle programmatically within an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the webhook to enable. This must be provided to specify which webhook should be activated. |
Output
The node outputs JSON data representing the result of the enable webhook operation. This typically includes confirmation details about the webhook status after enabling it. The exact structure depends on the SparkBot API response but generally confirms success or provides error information if enabling failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the SparkBot WhatsApp API.
- Needs network access to the SparkBot API endpoints.
- Proper configuration of the webhook URL on the SparkBot platform is assumed.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Webhook ID will cause the operation to fail.
- Network connectivity problems can prevent successful API calls.
- Insufficient permissions or incorrect API key may lead to authorization errors.
Error messages:
- Errors returned from the SparkBot API will be passed through; typical messages might indicate "Webhook not found" or "Unauthorized".
- If the node is set to continue on failure, errors will appear in the output JSON under an
errorfield.
Resolutions:
- Verify the Webhook ID is correct and corresponds to an existing webhook.
- Check API key validity and permissions.
- Ensure the SparkBot service is reachable from your environment.
Links and References
- SparkBot WhatsApp API Documentation (example link, replace with actual)
- n8n Webhook Node Concepts: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/