Actions83
- 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
Overview
This node integrates with the Commanders Act API, specifically allowing management of Mix Collect Redirect Rules among many other resources. The "Delete Redirect Rule" operation enables users to delete a specific redirect rule by its ID from the Mix Collect Redirect Rules resource.
This node is beneficial in scenarios where you need to programmatically manage redirect rules for data collection or tracking purposes within the Commanders Act platform. For example, if a redirect rule becomes obsolete or incorrect, this node can automate its removal without manual intervention in the Commanders Act dashboard.
Practical example:
- Automatically clean up redirect rules that are no longer valid as part of a workflow triggered by external events.
- Manage redirect rules dynamically based on changes in your marketing campaigns or website structure.
Properties
| Name | Meaning |
|---|---|
| Redirect Rule ID | The unique identifier of the redirect rule to delete. Required for delete, get, and update operations on redirect rules. |
| Query Parameters | Optional additional parameters to customize the API request. Includes options like start, end, filter, sort, page, and others for filtering or pagination. |
The "Query Parameters" property supports multiple optional fields such as:
start,end: Date/time range filters.filter: JSON object for complex filtering.sort: Sorting instructions.page: Pagination details.- Other filter options related to segments, devices, locations, etc.
Output
The output is a JSON array containing the response from the Commanders Act API after attempting to delete the specified redirect rule. The response typically includes:
- Confirmation of deletion or status code (e.g., "204 No Content" if successful with no content).
- If an error occurs, the node throws an error with details.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Commanders Act API.
- Requires credentials providing a site ID and an API token for authentication.
- The node uses HTTP requests to the Commanders Act API endpoint:
https://api.commander1.com/v2/{siteId}/ams/redirect-rules/{redirectRuleId}. - Proper configuration of the API credentials in n8n is necessary.
Troubleshooting
- Missing Redirect Rule ID: The node will throw an error if the Redirect Rule ID is not provided when required. Ensure this property is set.
- Authentication Errors: If API credentials are missing or invalid, the node will fail with an authentication error. Verify the API token and site ID.
- API Request Failures: Network issues or incorrect parameters may cause the API call to fail. Check the error message for details.
- Unexpected Response Format: If the API returns unexpected data, the node attempts to parse it; failure to parse JSON will result in raw text output or an error.
- Permission Issues: Ensure the API token has sufficient permissions to delete redirect rules.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- Commanders Act Mix Collect Redirect Rules API (specific resource documentation)
This summary focuses on the "Mix Collect Redirect Rule" resource and the "Delete Redirect Rule" operation as requested.