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 to manage Mix Collect Redirect Rules, specifically allowing users to update an existing redirect rule. It is useful in scenarios where you need to programmatically modify redirect rules for web traffic management or marketing tracking purposes within the Commanders Act platform.
For example, a marketing automation workflow might update redirect rules dynamically based on campaign parameters or user behavior analytics, ensuring that visitors are redirected appropriately without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Redirect Rule ID | The unique identifier of the redirect rule to update. This is required to specify which redirect rule to modify. |
| Query Parameters | Optional additional query parameters to customize the API request. Includes various filters and pagination options (e.g., end, filter[begin_date], page, sort). |
| Request Body | JSON object containing the data fields to update in the redirect rule. This should include the properties and values you want to change in the redirect rule. |
Output
The node outputs the JSON response from the Commanders Act API after updating the redirect rule. The output structure corresponds to the updated redirect rule's details as returned by the API. If the API returns no content, the node outputs a status code indicating "204 No Content".
No binary data output is involved.
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 using this node.
Troubleshooting
- Missing Redirect Rule ID: The node will throw an error if the Redirect Rule ID is not provided when attempting to update a redirect rule. Ensure this property is set.
- Invalid JSON in Request Body: The Request Body must be valid JSON. Invalid JSON will cause parsing errors.
- API Authentication Errors: If the API key credential is missing or invalid, the node will fail with an authentication error. Verify your API credentials.
- Unknown Resource or Operation: If the resource or operation names are incorrect or unsupported, the node will throw an error indicating an unknown resource or operation.
- Network or API Errors: Any network issues or API-side errors will be reported with the error message and stack trace for debugging.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n documentation on HTTP Request Node for understanding how API calls are made within workflows