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 → Delete Web Trigger
AI-generatedOverview
This node operation deletes a specific web trigger within the Commanders Act platform's Web Container resource. It is useful for managing and cleaning up web triggers that are no longer needed or relevant. For example, if a web trigger was set up for a campaign that has ended, this operation can remove it to keep the system organized.
Use Case Examples
- Deleting a web trigger by specifying its Trigger ID to remove it from the web container.
- Automating cleanup of outdated web triggers in a web container to maintain system hygiene.
Properties
| Name | Meaning |
|---|---|
| Trigger ID | The unique identifier of the web trigger to be deleted. |
| Query Parameters | Optional query parameters to customize the delete request, such as filters or pagination options. |
Output
JSON
Status Code- HTTP status code or message indicating the result of the delete operationjson- Response JSON object from the API if available
Dependencies
- Commanders Act API with API token and site ID credentials
Troubleshooting
- Ensure the Trigger ID is provided; otherwise, the node will throw an error indicating the missing Trigger ID.
- Verify that the API credentials (site ID and token) are correctly set and valid to avoid authentication errors.
- Check the API endpoint URL and query parameters for correctness to prevent request failures.
- If the API returns a 204 No Content status, it means the deletion was successful but no content is returned.