Actions24
- Campaign Actions
- Creative Actions
- Stats Actions
- Targeting Actions
Campaign → Get
AI-generatedOverview
The Kadam node integrates with the Kadam advertising platform API to manage and retrieve data related to advertising campaigns, creatives (ads), clients, targeting options, and statistics. Specifically, the Campaign - Get operation allows users to retrieve a list of advertising campaigns with optional filters and additional data inclusions.
This node is beneficial for marketing automation workflows where campaign data needs to be fetched dynamically for reporting, analysis, or further processing. For example, a user might want to pull all active campaigns along with their associated creatives and black/white lists to generate a comprehensive campaign report or synchronize campaign data with another system.
Properties
| Name | Meaning |
|---|---|
| Include Additional Data | Select additional data types to include in the campaign results. Options: Include Archived Campaigns, With Black/White Lists, With Creatives (Ads) |
| Campaign IDs | Filter campaigns by specific campaign IDs. Users can select multiple campaign IDs retrieved from "Get Campaigns". |
| Retry on Failure | If enabled, the node will retry the request up to 3 times on temporary failures such as rate limits or network issues. |
| Return All | If true, automatically paginate through all available results ignoring limit and offset parameters. |
| Limit | Maximum number of items to return per request when "Return All" is false. Defaults to 100. |
| Offset | Number of items to skip before starting to return results when "Return All" is false. Defaults to 0. |
| Output Fields | Optional comma-separated list of fields to include in the output JSON. If empty, all fields are returned. Example: id,name,status,link_url |
Output
The output is an array of JSON objects representing campaigns matching the query parameters. Each object contains campaign details such as ID, name, status, and other metadata. The exact fields included depend on the optional "Output Fields" property; if left empty, all available campaign fields are returned.
If additional data options are selected, the output may also include nested data structures for archived campaigns, black/white lists, or creatives (ads) associated with each campaign.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with the Kadam API.
- Network access to
https://api.kadam.net. - The node uses Axios HTTP client internally to make REST API calls.
- No additional environment variables are required beyond the configured API credentials.
Troubleshooting
Common Issues:
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Rate limiting or network timeouts: Enable "Retry on Failure" to allow automatic retries on transient errors.
- Empty results: Verify that the campaign IDs or filters used actually match existing campaigns.
- Invalid output fields: Using incorrect field names in "Output Fields" may result in missing data or errors.
Error Messages:
- Errors from the Kadam API are wrapped and surfaced with descriptive messages including HTTP status codes and API error descriptions.
- If the node encounters unexpected response formats, it attempts to wrap the data but logs warnings.
- When continuing on failure is disabled, any API or network error will cause the node execution to fail immediately with detailed error information.
Links and References
- Kadam API Documentation (official API endpoint base URL)
- Kadam API endpoints used:
/ads.campaigns.getfor retrieving campaigns
- n8n documentation on Creating Custom Nodes (for general understanding of node development)
This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.