Create an Hourly Benchmark Cooldown
Keep recurring benchmark activity spaced at a pace your systems can absorb.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Sleep
Sleep
Why this helps
Hourly jobs can bunch together when upstream 0CodeKit work varies in duration.
- Spreads recurring load
- Reduces collision risk
- Makes cadence easier to reason about
Setup
Build it in a few focused steps.
- 1Connect 0CodeKit and Bench in Notis once.
- 2Create a new automation called hourly benchmark cooldown.
- 3Describe the fixed sleep duration to apply on each scheduled run.
- 4Pick notis_cron and choose the hourly schedule.
- 5Select a report channel and test with one real hourly run.
Questions about this workflow
Is this tied to a 0CodeKit event?
No. 0CodeKit has no trigger events here, so the workflow starts from a Notis cron schedule.
Can I use a different cadence?
Yes. Choose another recurring cron schedule when creating or editing the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 0CodeKit to Bench. A trigger fires from one place; an action lands in another.
0CodeKit 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.
0CodeKit 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.