Actions24
- Campaign Actions
- Creative Actions
- Stats Actions
- Targeting Actions
Targeting → Get Browsers
AI-generatedOverview
This node interacts with the Kadam API to retrieve various targeting-related data, specifically here focusing on the Get Browsers operation under the Targeting resource. It fetches a list of available browsers that can be used for ad targeting purposes in advertising campaigns.
Typical use cases include:
- Fetching browser options to dynamically populate targeting criteria in campaign setups.
- Integrating browser targeting data into automated workflows for ad campaign management.
- Filtering or segmenting audiences based on browser usage statistics.
For example, a marketing automation workflow might first call this node to get the list of browsers and then use those IDs to set up precise targeting rules in subsequent campaign creation or update steps.
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. Default is false. |
| Output Fields | Optional comma-separated list of fields to include in the response (e.g., id,title). If empty, all fields are returned. |
Output
The node outputs JSON data representing the list of browsers available for targeting. Each item typically includes fields like:
id: Unique identifier of the browser.title: Human-readable name of the browser.
If the "Output Fields" property is specified, only those fields will be included in each browser object; otherwise, all available fields are returned.
The output is an array of objects, each corresponding to one browser option usable in targeting configurations.
No binary data output is produced by this operation.
Dependencies
- Requires an active Kadam API credential with an API token and application ID configured in n8n.
- The node makes HTTP GET requests to the Kadam API endpoint for targeting browsers.
- Network connectivity to
https://api.kadam.netis required.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication errors.
- Network issues or Kadam API downtime may result in request failures.
- Specifying invalid field names in "Output Fields" may lead to incomplete or empty results.
Error Messages:
- Errors from the Kadam API are wrapped and surfaced with messages including HTTP status codes and error descriptions.
- Temporary failures (rate limits, network glitches) can be mitigated by enabling "Retry on Failure".
- If the node returns no data, verify that the API credentials have sufficient permissions and that the Kadam service is operational.
Links and References
- Kadam API Documentation (general reference for API endpoints)
- n8n Documentation on Creating Custom Nodes
- Kadam official website for more information about their advertising platform
This summary is based solely on static analysis of the provided source code and property definitions.