Actions24
- Campaign Actions
- Creative Actions
- Stats Actions
- Targeting Actions
Targeting → Get Devices
AI-generatedOverview
This node integrates with the Kadam API to retrieve various targeting-related data, specifically device types available for ad targeting. The "Get Devices" operation under the "Targeting" resource fetches a list of device types that can be used to refine advertising campaigns by device category.
Common scenarios where this node is beneficial include:
- Preparing campaign targeting criteria by understanding which device types are supported.
- Dynamically populating UI elements or dropdowns in workflows based on available devices.
- Filtering or segmenting ad delivery based on device type to optimize campaign performance.
For example, a user might use this node to get all device types and then filter their campaign bids or creatives to target only mobile devices or desktops.
Properties
| Name | Meaning |
|---|---|
| Retry on Failure | Boolean flag to retry the request up to 3 times on temporary failures such as rate limits or network issues. |
| Output Fields | Optional comma-separated list of fields to include in the response (e.g., id,title,parent). If empty, all fields are returned. |
Output
The output is a JSON array where each item represents a device type available for targeting. Each device object may contain fields such as:
id: Unique identifier of the device type.title: Human-readable name of the device type.parent: (Optional) Identifier or reference to a parent device category if applicable.
If the "Output Fields" property is specified, only those fields will be included in each device object; otherwise, all available fields are returned.
The node does not output binary data.
Example output JSON snippet:
[
{
"id": "1",
"title": "Mobile",
"parent": null
},
{
"id": "2",
"title": "Desktop",
"parent": null
}
]
Dependencies
- Requires an API key credential for authenticating with the Kadam API.
- The node makes HTTP requests to
https://api.kadam.net/ads.targeting.devices.get. - Proper configuration of the API token and application ID credentials is necessary.
- No additional environment variables are required.
Troubleshooting
- Temporary Failures / Rate Limits: If the API returns rate limit errors or network issues occur, enabling "Retry on Failure" helps by retrying the request up to 3 times.
- Invalid Credentials: Errors related to authentication usually indicate missing or incorrect API tokens or app IDs. Verify credentials in n8n settings.
- Empty or Unexpected Response: If no devices are returned or the response structure changes, check the API documentation or contact Kadam support.
- Malformed Output Fields: Specifying invalid field names in "Output Fields" may result in missing data or errors. Use valid field names like
id,title, andparent.
Links and References
- Kadam API Documentation (general reference for endpoints and parameters)
- Kadam official website for further support and API updates.
