Wait for remediation evidence before deciding
After remediation starts, pause long enough for meaningful evidence to accumulate.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Sleep
Sleep
Why this helps
Reviewing too soon can turn partial remediation evidence into a false conclusion.
- Avoids premature benchmark conclusions
- Sets a clear evidence collection period
- Makes remediation follow-up easier to time
Setup
Build it in a few focused steps.
- 1Connect 21risk and Bench in the Notis portal once.
- 2Create an automation named remediation evidence wait.
- 3Tell Notis to sleep in Bench for the evidence collection period after a 21risk webhook and report when it ends.
- 4Choose the webhook trigger and report destination.
- 5Test with one remediation notice.
Questions about this workflow
What information must the webhook include?
Include the remediation context and desired waiting period in the request or automation instruction.
Does this verify remediation?
No. It only creates the waiting period; verification still requires a later review of evidence.
Can different remediations use different waits?
Yes. Describe the appropriate duration in the incoming request or automation prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Bench. A trigger fires from one place; an action lands in another.
21risk triggers
Bench actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Sleep
Sleep
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Connect any two apps with Notis in the middle.
21risk and Bench, 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 Bench.