Commanders Act icon

Commanders Act

Use the Commanders Act API
Join our community

Actions108

Overview

This node integrates with the Commanders Act API, specifically allowing users to update a Web Tag within the "Web Container" resource. It sends an HTTP PATCH request to modify properties of an existing web tag identified by its Tag ID. This operation is useful for managing and updating tags used in web container management, such as adjusting tracking or marketing tags on websites.

Practical scenarios include:

  • Updating configuration details of a web tag without recreating it.
  • Modifying tag parameters dynamically based on workflow logic.
  • Automating tag updates across multiple containers or environments.

Properties

Name Meaning
Tag ID The unique identifier of the web tag to update.
Query Parameters Optional additional query parameters to customize the API request. Includes options like:
- End, Start (date/time filters)
- Fields[template]
- Filter (JSON object with various filter options such as date ranges, search terms, etc.)
- Granularity
- Include
- Page (pagination info in JSON)
- Sort (sorting criteria in JSON or string)
- Source
- Token (password type, likely for authentication or session token override)
Request Body JSON object containing the data to update the web tag with. This is the main payload sent in the PATCH request.

Output

The node outputs the JSON response from the Commanders Act API after attempting to update the web tag. The output structure depends on the API's response but generally includes the updated web tag details or status information.

If the API returns no content (HTTP 204), the node outputs a JSON object indicating "Status Code": "204 No Content".

No binary data output is involved in this operation.

Dependencies

  • Requires an active Commanders Act API credential with a valid site ID and API token.
  • The node uses the base URL https://api.commander1.com/v2.
  • Proper API permissions are necessary to update web tags.
  • Network access to the Commanders Act API endpoint must be available.

Troubleshooting

  • Missing Credentials: If the API credentials are not set or invalid, the node will throw an error indicating missing credentials.
  • Missing Tag ID: The operation requires a Tag ID; if omitted, the node throws an error stating that the Tag ID is required.
  • API Errors: Any errors returned by the Commanders Act API (e.g., authorization failures, invalid data) will be wrapped and reported as node API errors with descriptive messages.
  • Invalid JSON in Request Body: The request body must be valid JSON; otherwise, parsing errors may occur.
  • Network Issues: Connectivity problems to the API endpoint will cause request failures.

To resolve these issues:

  • Ensure credentials are correctly configured.
  • Provide all required parameters, especially Tag ID.
  • Validate JSON syntax in the request body.
  • Check network connectivity and API availability.

Links and References

Discussion