Commanders ActInstall

Overview

This node integrates with the Commanders Act API, specifically enabling interaction with various resources including Destinations. The "Get Destination" operation retrieves detailed information about a specific destination by its ID. This is useful for workflows that need to fetch configuration or metadata about destinations used in marketing integrations or data delivery pipelines managed within Commanders Act.

Practical examples:

• Fetching details of a marketing destination to verify its configuration before sending data.
• Retrieving destination info dynamically to use in conditional logic or reporting.
• Integrating destination metadata into broader automation workflows involving customer data platforms or analytics tools.

Properties

The Query Parameters collection supports these options (among others):

• End: End date/time filter.
• Fields[template]: Specify template fields to include.
• Filter: JSON filter object or individual filter fields like begin_date, end_date, search, segment_id, etc.
• Granularity: Level of detail for returned data.
• Include: Additional related data to include.
• Page: Pagination settings in JSON.
• Sort: Sorting criteria in JSON or string format.
• Source, Start, Token: Other optional query parameters for refined requests.

Output

The output is a JSON array where each item corresponds to the API response for a requested destination. The structure matches the Commanders Act API's destination object schema, typically including properties such as destination identifiers, configuration details, status, and metadata.

If the API returns binary data (not typical for this operation), it would be handled accordingly, but this operation primarily returns JSON data describing the destination.

Dependencies

• Requires an API key credential for authenticating with the Commanders Act API.
• The node uses the base URL https://api.commander1.com/v2.
• Proper configuration of credentials in n8n is necessary to authorize API calls.

Troubleshooting

• Missing Destination ID: If the Destination ID property is not set when required, the node throws an error indicating the missing parameter.
• Authentication Errors: Ensure the API key credential is correctly configured; otherwise, the node will fail with authentication errors.
• Invalid Query Parameters: Malformed JSON or unsupported query parameters may cause API errors.
• API Rate Limits or Downtime: Network issues or rate limiting by the Commanders Act API can cause failures; retry or check API status.
• Unexpected Response Format: If the API returns unexpected data, parsing errors might occur; verify API version compatibility.

Links and References

• Commanders Act API Documentation (general reference for API endpoints and parameters)
• n8n documentation on HTTP Request Node for understanding underlying request mechanics (conceptual)