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 manage various resources related to digital marketing and data governance. Specifically, for the Web Container resource with the List Web Tags operation, it retrieves a list of web tags configured in the Commanders Act platform.

This functionality is useful for scenarios where you want to automate the retrieval and processing of web tag configurations, such as auditing tags on your website, synchronizing tag data with other systems, or triggering workflows based on tag information.

Example use cases:

  • Automatically fetch all web tags to monitor their status or configuration.
  • Integrate web tag data into reporting dashboards.
  • Use tag lists to trigger conditional logic in marketing automation workflows.

Properties

Name Meaning
Query Parameters A collection of optional parameters to filter, sort, paginate, or specify fields in the API request. Options include: end, Fields[template], filter (and various filter subfields like begin_date, end_date, search, etc.), granularity, include, page, sort, source, start, and token. These allow fine control over which web tags are returned and how results are formatted.

Output

The node outputs an array of JSON objects representing the web tags retrieved from the Commanders Act API. Each object corresponds to a web tag with its associated properties as defined by the API response.

If the API returns binary data (not typical for this operation), the node would handle it accordingly, but for listing web tags, the output is purely JSON.

Dependencies

  • Requires an API key credential for authenticating with the Commanders Act API.
  • The node makes HTTP requests to the base URL https://api.commander1.com/v2.
  • No additional external dependencies beyond standard HTTP and JSON handling.

Troubleshooting

  • Missing Credentials Error: If the API credentials are not set or invalid, the node will throw an error indicating missing credentials. Ensure that a valid API authentication token is configured.
  • Required Parameter Missing: For some operations, specific IDs or parameters are mandatory. For example, if a required ID parameter is missing, the node throws an error specifying which parameter is needed.
  • API Request Errors: Network issues, invalid query parameters, or API limits may cause errors. The node surfaces these with descriptive messages including the original error message and stack trace.
  • Empty or Unexpected Response: If the API returns no content or unexpected data, the node handles it gracefully but verify the query parameters and API status.

Links and References

This summary focuses on the "Web Container" resource and the "List Web Tags" operation, describing the input parameters, output structure, and relevant details extracted from the static source code analysis.

Discussion