Actions108
- Activity Log Actions
- Consent Analysis Actions
- Cookie Scanner Actions
- Web Container Actions
- Get Web Tag
- 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 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
- 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 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
Web Container → Get Web Constraint
AI-generatedOverview
This node interacts with the Commanders Act API to manage web containers, specifically to get details of a web constraint by its ID. It is useful for retrieving specific configuration or constraint information related to web containers in the Commanders Act platform, which can be used for web tag management and related operations.
Use Case Examples
- Retrieve details of a specific web constraint by providing its Constraint ID to monitor or audit web container configurations.
- Use the node to fetch web constraint data as part of an automated workflow for managing web container settings.
Properties
| Name | Meaning |
|---|---|
| Constraint ID | The unique identifier of the web constraint to retrieve. This is required to specify which web constraint to get. |
| Query Parameters | Optional query parameters to refine or filter the API request when getting the web constraint. Includes parameters like 'end', 'filter', 'granularity', 'include', 'page', 'sort', 'source', 'start', and 'token'. |
Output
JSON
json- The JSON response from the Commanders Act API containing the details of the requested web constraint.
Dependencies
- Commanders Act API credentials (siteId and tokenAPI) required for authentication.
Troubleshooting
- Ensure the Constraint ID is provided; otherwise, the node will throw an error indicating the missing Constraint ID.
- Verify that the Commanders Act API credentials are correctly configured and valid to avoid authentication errors.
- Check the API endpoint URL and query parameters for correctness to prevent request failures.
- If the API returns an error, the node will throw a NodeApiError with the message from the API; review the error message and stack trace for debugging.