Actions108
- Activity Log Actions
- Consent Analysis Actions
- Cookie Scanner Actions
- Data Cleansing Actions
- Destination Actions
- Event Delivery Actions
- Event Enrichment Actions
- Live Report Builder Actions
- Mix Collect Redirect Rule Actions
- Monitoring Actions
- Normalized Datalayer Actions
- Segment Actions
- Source Actions
- Sources Data Quality Actions
- User Actions
- Web Container Actions
- Create Web Constraint
- Create Web Container
- Create Web Perimeter
- Create Web Tag
- Create Web Trigger
- Delete Web Constraint
- Delete Web Container
- Delete Web Perimeter
- Delete Web Tag
- Delete Web Trigger
- Get Web Constraint
- Get Web Perimeter
- Get Web Tag
- Get Web Trigger
- List Web Constraints
- List Web Containers
- List Web Perimeters
- List Web Tags
- List Web Triggers
- Revert Web Tag
- Update Web Constraint
- Update Web Container
- Update Web Perimeter
- Update Web Tag
- Update Web Trigger
- Web Containers Variable Actions
- Create Web Datalayer Variables
- Create Web Datalayer Variables Category
- Create Web Internal Variables
- Delete Web Datalayer Variables
- Delete Web Datalayer Variables Category
- Delete Web Internal Variables
- Get Web Datalayer Variables
- Get Web Internal Variables
- List Web Datalayer Variables
- List Web Internal Variables
- Workspace Actions
Overview
This node integrates with the Commanders Act API, specifically enabling interaction with various resources and operations provided by the platform. For the Destination resource with the List Catalog Destinations operation, it fetches a list of catalog destinations available in the Commanders Act system.
This functionality is useful when you want to retrieve and work with the catalog of available destinations for integrations or data delivery within your marketing or analytics workflows. For example, you might use this node to dynamically populate options in a workflow based on available destinations or to audit and analyze the destinations configured in your Commanders Act account.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | A collection of optional query parameters to filter, sort, paginate, or customize the API response. Supported parameters include: end, Fields[template], filter (and its subfields like begin_date, end_date, search, etc.), granularity, include, page, sort, source, start, and token. These allow fine control over the data returned from the catalog destinations list endpoint. |
The full list of query parameters supported (as per the property definition) includes:
- End
- Fields[template]
- Filter (with nested filters such as begin_date, end_date, from, rangeType, search, segment_id, sup_filters for device and location, to, types)
- Granularity
- Include
- Page
- Sort (including specific sorts for event enrichments and live report builder)
- Source
- Start
- Token (a password-type field)
Output
The output is an array of JSON objects representing the catalog destinations retrieved from the Commanders Act API. Each item corresponds to a destination entry as returned by the API's /integration-categories endpoint.
If the API returns no content, the node outputs a status code message indicating "204 No Content".
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Commanders Act API.
- Requires valid API credentials including a site identifier and an API token.
- The node uses HTTP requests to the base URL
https://api.commander1.com/v2. - The user must configure the node with appropriate credentials that provide access to the Commanders Act API.
Troubleshooting
- Missing Credentials Error: If the API credentials are not set or invalid, the node will throw an error indicating missing credentials. Ensure that the API key/token and site ID are correctly configured.
- Required Parameter Missing: Some operations require specific IDs or parameters; if these are missing, the node throws an error specifying which parameter is required.
- API Request Errors: Network issues, invalid query parameters, or API limits may cause errors. The node surfaces these as API errors with messages and stack traces.
- Parsing Errors: If the API returns malformed JSON or unexpected responses, the node attempts to parse but may fallback to returning raw text or status codes.
- To resolve errors, verify all required parameters, check API credentials, and ensure network connectivity.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n documentation on HTTP Request Node for understanding how API calls are made internally.
This summary focuses exclusively on the Destination resource and the List Catalog Destinations operation as requested.