Pause Before a Benchmark Rate Limit Window
Give bursty benchmark jobs a predictable breathing room before the next step runs.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Sleep
Sleep
Why this helps
Rapid requests can collide with provider limits and create avoidable retries.
- Reduces burst pressure
- Creates predictable pacing
- Cuts manual retry work
Setup
Build it in a few focused steps.
- 1Connect 0CodeKit and Bench in Notis once.
- 2Create a new automation and name this rate limit pause.
- 3Tell Notis to sleep for the delay stated in each incoming webhook request.
- 4Pick the notis_webhook trigger and choose where run reports go.
- 5Test with one real 0CodeKit request that includes a delay value.
Questions about this workflow
How is the delay chosen?
Include the desired delay in the webhook request or state a fixed delay in the automation prompt.
Does this call a Bench benchmark?
No. This workflow only runs the Bench Sleep action, so use it as a pacing step in a larger 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.