Clean up a specifically confirmed obsolete alert
Retire a known obsolete alert with the exact identifiers and confirmation needed to avoid deleting the wrong one.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Delete Pipeline Alert
Tool to delete an alert for a specific component within a pipeline. use after confirming pipeline id, component kind, component id, and alert id.
Why this helps
Old alerts can add noise and make it harder to focus on the pipeline signals that still need attention.
- Remove a confirmed obsolete alert from a specified component.
- Reduce noise from alerts that no longer apply.
- Keep cleanup tied to explicit identifiers and confirmation.
Setup
Build it in a few focused steps.
- 1Connect Mezmo to Notis once through the portal; connect Verifi.Email if its process supplies the cleanup request.
- 2Create an automation in the portal or ask Notis conversationally to handle confirmed cleanup requests.
- 3Use one prompt requiring confirmation and the exact pipeline ID, component kind, component ID, and alert ID before deletion.
- 4Select an incoming webhook trigger and a channel for run reports.
- 5Test only with a real, explicitly confirmed obsolete alert and verify the intended alert was removed.
Questions about this workflow
What information is required before deleting an alert?
The workflow must confirm the pipeline ID, component kind, component ID, and alert ID.
Will it delete alerts based only on a Verifi.Email result?
No. Deletion should happen only when a webhook request explicitly confirms cleanup and provides the exact identifiers.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Verifi.Email to Mezmo. A trigger fires from one place; an action lands in another.
Verifi.Email triggers
Mezmo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Pipeline Alert
Tool to delete an alert for a specific component within a pipeline. use after confirming pipeline id, component kind, component id, and alert id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Ingest logs to Mezmo
Tool to ingest log events to mezmo. use when sending structured logs from a host to mezmo log analysis.
Connect any two apps with Notis in the middle.
Verifi.Email and Mezmo, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Mezmo.