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 → Create Redirect Rule
AI-generatedOverview
This node interacts with the Commanders Act API to create a new Mix Collect Redirect Rule. It is useful for users who want to programmatically manage redirect rules within the Mix Collect feature of Commanders Act, enabling automated setup of redirect behaviors based on specified criteria.
Use Case Examples
- Automatically create redirect rules for marketing campaigns to track user redirections.
- Set up redirect rules dynamically based on user input or external triggers in an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional query parameters to customize the API request, such as filters, pagination, sorting, and other parameters relevant to the redirect rule creation. |
| Request Body | JSON object representing the body of the request to create the redirect rule, containing the details and configuration of the redirect rule to be created. |
Output
JSON
id- The unique identifier of the created redirect rule.name- The name of the created redirect rule.sourceUrl- The source URL that triggers the redirect.targetUrl- The target URL to which the redirect points.status- The status of the redirect rule (e.g., active, inactive).createdAt- Timestamp when the redirect rule was created.updatedAt- Timestamp when the redirect rule was last updated.
Dependencies
- Commanders Act API with API token credentials
Troubleshooting
- Ensure that the API credentials (siteId and tokenAPI) are correctly set and valid, as missing or invalid credentials will cause authentication errors.
- Verify that the required fields in the request body are correctly formatted JSON and include all necessary properties for creating a redirect rule.
- Check that the Redirect Rule ID is not required for creation but is required for update, get, or delete operations to avoid errors.
- If the API returns errors, inspect the error message and stack trace provided by the node for debugging.