Add a Nightly Benchmark Settling Window
Let overnight processing settle before your benchmark routine moves forward.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Sleep
Sleep
Why this helps
Scheduled jobs can start while document or data conversion work is still finishing.
- Separates overnight workloads
- Makes run timing consistent
- Prevents premature follow up
Setup
Build it in a few focused steps.
- 1Connect 0CodeKit and Bench in Notis once.
- 2Create a new automation named nightly settling window.
- 3Describe the sleep duration and explain that it follows the overnight 0CodeKit workload.
- 4Pick the notis_cron trigger and set the recurring schedule.
- 5Choose a report channel and test with one real scheduled run.
Questions about this workflow
Can I change the nightly time later?
Yes. Edit the automation schedule in Notis and keep the sleep duration in its prompt.
What does Notis use as the source event?
This workflow uses a recurring Notis cron schedule because 0CodeKit exposes no trigger events.
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.