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
This node interacts with the SparkBot WhatsApp API, providing various operations grouped by resource types. Specifically, for the Campaigns resource and the Delete Campaign operation, it allows users to delete a campaign by specifying its unique campaign ID.
Common scenarios where this node is beneficial include managing marketing or communication campaigns on WhatsApp via SparkBot. For example, if a campaign is no longer needed or was created in error, this operation can remove it from the system programmatically within an automation workflow.
Practical example: An automated workflow that cleans up outdated campaigns every month by deleting campaigns whose IDs are retrieved from a database or previous steps.
Properties
| Name | Meaning |
|---|---|
| Campaign ID | The unique identifier of the campaign to delete |
Output
The output of the node is a JSON object representing the response from the SparkBot API after attempting to delete the specified campaign. Typically, this will confirm whether the deletion was successful or provide details about any errors encountered.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the SparkBot WhatsApp API.
- The node depends on the SparkBot API service being accessible and the provided campaign ID being valid.
- No additional environment variables or external services are explicitly required beyond the API key.
Troubleshooting
Common issues:
- Providing an invalid or non-existent campaign ID will likely result in an error from the API.
- Network connectivity problems may prevent the node from reaching the SparkBot API.
- Missing or incorrect API key credentials will cause authentication failures.
Error messages and resolutions:
- "Campaign not found" — Verify the campaign ID is correct and exists.
- "Authentication failed" — Check that the API key credential is correctly configured and valid.
- Timeout or network errors — Ensure stable internet connection and that the SparkBot API endpoint is reachable.
Links and References
- SparkBot WhatsApp API Documentation (example placeholder link)
- n8n documentation on creating custom nodes