Commanders Act icon

Commanders Act

Use the Commanders Act API

Actions83

Overview

This node integrates with the Commanders Act API, allowing users to manage and interact with various resources provided by the Commanders Act platform. It supports a wide range of operations across multiple resources such as Sources, Activity Logs, Consent Analysis, Cookie Scanner, Data Cleansing, Destinations, Event Delivery, Event Enrichments, Live Reports, Monitoring, Segments, Web Containers, Workspaces, and more.

For the Source resource with the Get Source operation, this node fetches detailed information about a specific source identified by its Source ID. This is useful for scenarios where you want to retrieve metadata or configuration details about a particular data source integrated into your Commanders Act environment.

Practical examples include:

  • Retrieving configuration details of a marketing data source.
  • Fetching source-specific statistics or settings before performing further processing.
  • Automating audits or synchronization tasks involving sources in Commanders Act.

Properties

Name Meaning
Source ID The unique identifier of the source to get information about. Required for operations that target a specific source (e.g., Get, Delete, Update).
Query Parameters A collection of optional query parameters to customize the API request. These include:
- End
- Fields[template]
- Filter (JSON)
- Filter[begin_date]
- Filter[end_date]
- Filter[from]
- Filter[rangeType]
- Filter[search]
- Filter[segment_id]
- Filter[sup_filters][device][]
- Filter[sup_filters][location][]
- Filter[to]
- Filter[types]
- Granularity
- Include
- Page (JSON)
- Sort (JSON or string)
- Source
- Start
- Token (password type)
These parameters allow filtering, sorting, pagination, and other customizations of the request.

Output

The node outputs an array of JSON objects representing the response from the Commanders Act API for the requested operation. For the "Get Source" operation, the output JSON contains detailed information about the specified source, including its properties and metadata as returned by the API.

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

Example output structure (simplified):

{
  "id": "source-id",
  "name": "Source Name",
  "type": "source-type",
  "configuration": { /* source-specific config */ },
  "createdAt": "timestamp",
  "updatedAt": "timestamp",
  ...
}

Dependencies

  • Requires an API key credential for authenticating with the Commanders Act API.
  • The node uses the base URL https://api.commander1.com/v2.
  • No additional external dependencies beyond the API credentials and network 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 you have configured a valid API authentication token.
  • Required Parameter Missing: For operations like "Get Source," if the Source ID is not provided, the node throws an error specifying the missing parameter. Always provide required IDs for targeted operations.
  • API Request Failures: Network issues, invalid tokens, or incorrect parameters can cause API errors. The node surfaces these errors with messages prefixed by "Error calling Commanders Act API." Check the message and stack trace for details.
  • Invalid JSON in Request Body: For operations requiring a request body, ensure the JSON is well-formed; otherwise, parsing errors may occur.
  • Unexpected Response Format: If the API returns a non-JSON response, the node attempts to parse it; if parsing fails, it returns the raw text.

Links and References

This summary focuses specifically on the Source resource and the Get Source operation as requested.

Discussion