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
Mix Collect Redirect Rule → Delete Redirect Rule
AI-generatedOverview
This node interacts with the Commanders Act API to delete a specific Mix Collect Redirect Rule. It is useful in scenarios where you need to programmatically remove redirect rules from your Commanders Act setup, such as cleaning up outdated or incorrect redirect rules. For example, if a redirect rule is no longer valid or needed, this node can be used to delete it by specifying its Redirect Rule ID.
Use Case Examples
- Deleting a redirect rule by providing its Redirect Rule ID to maintain an up-to-date set of redirect rules in your Commanders Act environment.
- Automating the cleanup of redirect rules as part of a workflow that manages website redirects dynamically.
Properties
| Name | Meaning |
|---|---|
| Redirect Rule ID | The unique identifier of the redirect rule to be deleted. This is required to specify which redirect rule to remove. |
| Query Parameters | Optional query parameters to customize the API request, such as filtering or pagination options. |
Output
JSON
Status Code- Indicates the HTTP status code or response status of the delete operation, e.g., '204 No Content' for successful deletion.
Dependencies
- Commanders Act API with API token and site ID credentials
Troubleshooting
- Ensure the Redirect Rule ID is provided; otherwise, the node throws an error indicating the missing ID.
- Check API credentials (site ID and token) are correctly set to avoid authentication errors.
- Verify the Redirect Rule ID exists and is accessible with the provided credentials to prevent 'not found' or permission errors.
Links
- Commanders Act API - Delete Redirect Rule - Official API documentation for deleting a Mix Collect Redirect Rule in Commanders Act.