Create a calm pause before incident review
Use a defined cooloff period so incident review begins with organized evidence and a clear head.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Sleep
Sleep
Why this helps
Immediate incident reactions can duplicate work and amplify incomplete information.
- Creates a consistent response pause
- Reduces duplicate early investigations
- Gives evidence time to consolidate
Setup
Build it in a few focused steps.
- 1Connect 21risk and Bench in the Notis portal once.
- 2Create an automation named incident review cooloff.
- 3Tell Notis to run Bench Sleep for the agreed cooloff period after a 21risk webhook and report completion.
- 4Select the webhook trigger and report channel.
- 5Test with one incident notice.
Questions about this workflow
Is this an incident response system?
No. It supplies a deliberate waiting step before your existing review process.
How long should the cooloff be?
Choose a duration that matches your incident process and state it in the instruction.
Can the webhook be called manually?
Yes. A webhook starts the automation when your system sends an HTTP request.
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.