Commanders Act icon

Commanders Act

Use the Commanders Act API
Join our community

Actions108

Overview

This node integrates with the Commanders Act API, allowing users to interact with various resources and operations provided by the platform. Specifically, for the Destination resource and the List Destination Categories operation, it fetches a list of destination categories available in the Commanders Act system.

This node is beneficial when you want to automate workflows involving marketing or data integration platforms managed through Commanders Act. For example, you might use it to retrieve destination categories to dynamically populate options in subsequent workflow steps or to audit available destinations for reporting purposes.

Properties

Name Meaning
Query Parameters A collection of optional query parameters to filter or modify the request. These include:
- End (string): End date/time filter
- Fields[template] (string): Template fields selection
- Filter (JSON): Complex filter criteria
- Filter[begin_date], Filter[end_date], Filter[from], Filter[to] (string): Date range filters
- Filter[rangeType] (string): Type of range filter
- Filter[search] (string): Search term
- Filter[segment_id] (string): Segment identifier
- Filter[sup_filters][device][] (string): Device filters
- Filter[sup_filters][location][] (string): Location filters
- Filter[types] (string): Types filter
- Granularity (string): Data granularity level
- Include (string): Additional related data to include
- Page (JSON): Pagination details
- Sort (JSON/string): Sorting criteria
- Source (string): Source identifier
- Start (string): Start date/time filter
- Token (string, password type): Optional token for authentication or filtering

These parameters allow fine-tuning the API request to retrieve specific subsets or views of destination categories.

Output

The node outputs an array of JSON objects representing the destination categories retrieved from the Commanders Act API. Each object corresponds to a category with its associated properties as returned by the API.

If the API returns binary data (not typical for this operation), it would be handled accordingly, but for listing destination categories, the output is purely JSON.

Dependencies

  • Requires an active Commanders Act API credential with a valid site ID and API token.
  • The node makes HTTP requests to https://api.commander1.com/v2.
  • Proper configuration of credentials in n8n is necessary to authenticate API calls.

Troubleshooting

  • Missing Credentials Error: If the node throws "Missing Commanders Act API Credentials," ensure that the API key credential is configured correctly in n8n.
  • Required Parameter Missing: Some operations require specific IDs or parameters; if missing, the node will throw errors indicating which parameter is required.
  • API Request Failures: Network issues or invalid tokens can cause request failures. Check connectivity and credential validity.
  • Parsing Errors: If the API response is not valid JSON, the node attempts to handle it gracefully, but unexpected formats may cause errors.

Links and References

Discussion