Commanders Act icon

Commanders Act

Use the Commanders Act API
Join our community

Actions108

Overview

This node integrates with the Commanders Act API, specifically managing "Web Container" resources. The "Update Web Constraint" operation allows users to update an existing web constraint by specifying its ID and providing updated data in the request body. This is useful for modifying rules or conditions that govern web container behavior, such as access controls, filtering, or other constraints applied within a web container environment.

Practical scenarios include:

  • Updating security or access constraints on a web container.
  • Modifying filtering rules or parameters dynamically based on new requirements.
  • Automating updates to web container configurations as part of a larger workflow.

Properties

Name Meaning
Constraint ID The unique identifier of the web constraint to update.
Query Parameters Optional additional query parameters to refine or control the API request.
Request Body JSON object containing the fields and values to update in the web constraint.

The Query Parameters collection supports various optional parameters (like filters, pagination, sorting, date ranges, etc.) but their specific use depends on the API endpoint and are generally used to customize the request further.

Output

The node outputs the JSON response from the Commanders Act API after updating the web constraint. The output structure corresponds directly to the API's response schema for the updated web constraint resource, typically including details of the updated constraint such as its ID, properties, status, and any metadata returned by the API.

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

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 the API credentials in n8n is necessary before using this node.

Troubleshooting

  • Missing Constraint ID: If the "Constraint ID" property is not provided, the node will throw an error indicating it is required.
  • Invalid JSON in Request Body: The request body must be valid JSON; otherwise, parsing errors will occur.
  • API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Network or API Errors: The node wraps API call errors and provides messages prefixed with "Error calling Commanders Act API". Check network connectivity and API status.
  • Unexpected Response Format: If the API returns a string instead of JSON, the node attempts to parse it; if parsing fails, it returns the raw text.

Links and References

Discussion