Actions24
- Campaign Actions
- Creative Actions
- Stats Actions
- Targeting Actions
Campaign → Delete
AI-generatedOverview
This node integrates with the Kadam API to manage advertising campaigns, including creating, updating, retrieving statistics, and deleting campaigns. Specifically, the Delete Campaign operation allows users to delete one or more existing campaigns by specifying their IDs.
Common scenarios for this node include:
- Automating campaign lifecycle management by programmatically removing outdated or completed campaigns.
- Cleaning up test or temporary campaigns in bulk.
- Integrating campaign deletion into larger marketing workflows where campaigns are dynamically created and removed based on business logic.
Example use case:
- A marketing team uses this node to delete multiple campaigns that have ended or failed performance criteria, ensuring the ad platform remains organized and only active campaigns consume resources.
Properties
| Name | Meaning |
|---|---|
| IDs | List of campaign IDs to delete. Users can select multiple campaigns from a dynamically loaded list. Use the "Get Campaigns" operation to retrieve available campaign IDs. |
| Retry on Failure | Boolean option to retry the delete request up to 3 times if temporary failures occur (e.g., rate limits or network issues). |
Output
The output is an array of JSON objects corresponding to each input item processed. Each object contains the result of the delete operation for the specified campaign IDs. The structure typically includes success or error information:
- On success: JSON indicating successful deletion.
- On failure: JSON containing error details such as message, description, resource, operation, timestamp, HTTP status code, and any API error data returned.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Kadam API.
- The node makes HTTP requests to
https://api.kadam.netendpoints. - Proper configuration of the API token and application ID credentials is necessary.
- Network connectivity to the Kadam API service must be available.
Troubleshooting
Common Issues:
- Invalid or expired API token causing authentication failures.
- Specifying campaign IDs that do not exist or belong to another client.
- Network timeouts or rate limiting by the Kadam API.
Error Messages:
"API Error: <error_desc>": Indicates an error response from the Kadam API. Check the error description for details."Unsupported resource": Occurs if the resource parameter is incorrect; ensure "Campaign" is selected."Failed to load campaign categories"or similar loading errors indicate issues fetching dynamic options, possibly due to credential problems.
Resolutions:
- Verify API credentials and permissions.
- Confirm campaign IDs are correct and accessible.
- Enable "Retry on Failure" to handle transient network or rate limit errors.
- Review API quota and usage limits on the Kadam platform.
Links and References
- Kadam API Documentation (general reference): https://api.kadam.net/docs (assumed, not explicitly in code)
- n8n Documentation on Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/
- Axios HTTP Client (used internally): https://axios-http.com/
This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.