Actions108
- Activity Log Actions
- Consent Analysis Actions
- Cookie Scanner Actions
- Data Cleansing Actions
- Destination Actions
- Event Delivery Actions
- Event Enrichment Actions
- Live Report Builder Actions
- Mix Collect Redirect Rule Actions
- Monitoring Actions
- Normalized Datalayer Actions
- Segment Actions
- Source Actions
- Sources Data Quality Actions
- User Actions
- Web Container Actions
- Create Web Constraint
- Create Web Container
- Create Web Perimeter
- Create Web Tag
- Create Web Trigger
- Delete Web Constraint
- Delete Web Container
- Delete Web Perimeter
- Delete Web Tag
- Delete Web Trigger
- Get Web Constraint
- Get Web Perimeter
- Get Web Tag
- Get Web Trigger
- List Web Constraints
- List Web Containers
- List Web Perimeters
- List Web Tags
- List Web Triggers
- Revert Web Tag
- Update Web Constraint
- Update Web Container
- Update Web Perimeter
- Update Web Tag
- Update Web Trigger
- Web Containers Variable Actions
- Create Web Datalayer Variables
- Create Web Datalayer Variables Category
- Create Web Internal Variables
- Delete Web Datalayer Variables
- Delete Web Datalayer Variables Category
- Delete Web Internal Variables
- Get Web Datalayer Variables
- Get Web Internal Variables
- List Web Datalayer Variables
- List Web Internal Variables
- Workspace Actions
Overview
This node integrates with the Commanders Act API, specifically allowing users to list web constraints within the "Web Container" resource. It enables retrieval of web constraint data by sending requests to the Commanders Act platform, which is useful for managing and auditing web container configurations.
Common scenarios include:
- Fetching a list of web constraints to monitor or audit web container rules.
- Filtering or sorting constraints based on various query parameters.
- Integrating web container data into workflows for compliance, reporting, or automation purposes.
For example, a user might want to retrieve all active web constraints applied to a specific container or within a date range to analyze their impact on website behavior.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | A collection of optional parameters to customize the request. These include: - End (string) - Fields[template] (string) - Filter (JSON) - Filter[begin_date] (string) - Filter[end_date] (string) - Filter[from] (string) - Filter[rangeType] (string) - Filter[search] (string) - Filter[segment_id] (string) - Filter[sup_filters][device][] (string) - Filter[sup_filters][location][] (string) - Filter[to] (string) - Filter[types] (string) - Granularity (string) - Include (string) - Page (JSON) - Sort (JSON or string depending on context) - Source (string) - Start (string) - Token (string, password type) These parameters allow filtering, pagination, sorting, and specifying fields in the API request. |
Output
The node outputs an array of JSON objects representing the web constraints retrieved from the Commanders Act API. Each object corresponds to a web constraint entity with its associated properties as returned by the API.
If the API returns no content, the output will indicate a "204 No Content" status.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Commanders Act API.
- The node uses the base URL
https://api.commander1.com/v2for all requests. - Proper configuration of the API credentials in n8n is necessary before use.
Troubleshooting
- Missing Credentials: If the API key credential is not set or invalid, the node will throw an error indicating missing credentials.
- Required Parameter Missing: For this operation, if required identifiers (like Constraint ID for other operations) are missing, the node throws an error. For listing web constraints, no such ID is required.
- API Errors: Any errors returned by the Commanders Act API will be wrapped and reported with details. Check the error message and stack trace for troubleshooting.
- Empty Response: If the API returns no data, the node outputs a "204 No Content" status. Verify query parameters or API availability.
Links and References
- Commanders Act API Documentation (general reference; specific endpoints may require login)
- n8n documentation on HTTP Request Node for understanding API calls
- Commanders Act official site: https://www.commandersact.com/