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 → Create Web Perimeter
AI-generatedOverview
This node interacts with the Commanders Act API to create a web perimeter within the Web Container resource. It is useful for users who want to programmatically manage web perimeters in their Commanders Act environment, such as setting up security or access boundaries for web containers.
Use Case Examples
- Creating a new web perimeter with specific configuration details provided in the request body to control access or define boundaries within a web container.
- Automating the creation of web perimeters as part of a larger workflow for managing web containers and their associated constraints, tags, or triggers.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional query parameters to customize the API request, such as filtering, pagination, sorting, and other specific parameters relevant to the web perimeter creation endpoint. |
| Request Body | JSON object containing the details of the web perimeter to be created, such as configuration settings and attributes relevant to the perimeter. |
Output
JSON
json- The JSON response from the Commanders Act API representing the created web perimeter or the result of the API call.
Dependencies
- Commanders Act API credentials (siteId and tokenAPI) required for authentication.
Troubleshooting
- Ensure that the Commanders Act API credentials are correctly configured and provided; missing credentials will cause an error.
- Verify that the required parameters such as siteId and tokenAPI are valid and have the necessary permissions to create a web perimeter.
- Check that the request body JSON is correctly formatted and contains all required fields for creating a web perimeter.
- If the API returns an error, review the error message for details and ensure the API endpoint URL is correctly constructed with the siteId and query parameters.
- Network issues or API downtime can cause request failures; verify network connectivity and API service status.