Delay Bench after company detail retrieval
Let a burst of company lookups settle before Bench resumes.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Sleep
Sleep
Why this helps
Large lookup bursts can make downstream automation noisy and difficult to sequence.
- Smooths bursts of lookup requests
- Improves run sequencing
- Reduces context switching during busy research periods
Setup
Build it in a few focused steps.
- 1Connect 44API and Bench once in the Notis portal.
- 2Create an automation and tell Notis to run a Bench Sleep action after company details arrive.
- 3Pick the webhook trigger and include the pause duration in plain language.
- 4Choose the report channel for run updates.
- 5Test with one real company detail response.
Questions about this workflow
Will the company details be changed?
No. The workflow only pauses the Bench action; it does not edit 44API data.
What starts this workflow?
An HTTP request to the Notis webhook starts it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 44API to Bench. A trigger fires from one place; an action lands in another.
44API 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.
44API 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.