Describe the outcome
Name the inputs, destination, trigger, time zone and exceptions. Say what the workflow must not do. Describe it here and Whenever writes it, start from a template, or bring the brief to your coding agent.
Whenever · AI workflow builder
From a brief to a workflow you can read.
Describe the process in plain words and Whenever’s AI writes it as a typed workflow. Test it against real inputs, publish the trigger, and from then on it runs as code. The only model call in a run is one you chose to put in a step.
A useful brief starts with the rules
“Every weekday, tell us what needs attention.”
Every weekday at 09:00 Europe/Vilnius, read our customer-onboarding sheet. Select rows marked blocked, grouped by owner. Post one summary to the onboarding Slack channel. If there are no blocked rows, post nothing. If an owner is missing, flag that row for review. Do not edit the sheet.
Example brief, not executable SDK code. Connect the actual sheet and channel, review permissions, and verify the generated workflow before publishing.
The readable flow
- ScheduleWeekdays · 09:00
Explicit Europe/Vilnius time zone.
- ReadFetch sheet rows
Use the authorized spreadsheet connection.
- RulesFilter & group
Blocked only. Missing owners flagged. Empty means stop.
- ActionPost a summary
One destination. No spreadsheet writes.
From a sentence to a running process.
The brief is the beginning, not the acceptance test. Keep the important decisions visible at each handoff.
Review the typed workflow
Whenever workflows are TypeScript modules with a trigger manifest and a runnable workflow. Inspect branches, named steps and integration calls instead of relying on the prompt alone.
Test representative inputs
Run manually against controlled data and a test destination. Try the ordinary case, the empty case and the missing-field case. Inspect the actual output before connecting live actions.
Publish the trigger
Choose a schedule, webhook or supported provider event. Authorize the required connections, check run history and keep an owner responsible for exceptions.
Before this runs without you
Use this as the review checklist for your first workflow.
- The trigger and time zone match the business deadline.
- Input shape, missing values and empty results have explicit handling.
- Only the intended connections and destinations are authorized.
- Any AI output is validated before it can cause an action.
- Retries cannot silently create duplicate business records.
- A failed run has an owner and a useful record to investigate.
For processes that have a repeatable shape.
A good fit
- Operators turning a recurring report into a scheduled workflow.
- Technical teams that want readable TypeScript and explicit integration calls.
- Builders who use a coding agent and need a place to publish the result.
Choose something else when…
- The task is mainly open-ended research with no known sequence of steps.
- You want a finished app without reviewing permissions, outputs or failure cases.
- You need an export that runs unchanged on another provider: runtime-specific ports and triggers may need adaptation.
Build with the published plan in view.
The same plans and allowances as our pricing page. Model usage and external services belong in your estimate too.
Hobby
$0/mo
100 runs per month
One active workflow, no credit card.
* One run = one workflow execution, start to finish. Free AI building and editing have weekly usage limits.
A few useful answers
What does an AI workflow builder do?
It helps turn a plain-language description into an automation. In Whenever, the result is a typed workflow with explicit triggers and logic. You still review its actions, authorize connections and test real inputs before publishing.
Do I have to start by writing code?
You can start with a brief, a template or your coding agent. The workflow itself is TypeScript, so code remains available to inspect and change. Someone should review the logic and permissions before it handles live business data.
Does every workflow run need an AI call?
No. AI can help write a workflow that uses only explicit rules and API calls at runtime. If the process needs interpretation, add a bounded AI step and validate its output before downstream actions.
What can trigger a Whenever workflow?
The documented trigger builders include manual runs, schedules, one-time runs, webhooks and managed provider events. Provider events and integration actions depend on the connections available and authorized in your workspace.
Can I move the generated workflow to another runtime?
You can inspect and adapt the TypeScript logic. Do not assume it is a drop-in deployment elsewhere: integration ports, triggers, credentials and step execution depend on the runtime.
Sources & further reading
Sources reviewed September 24, 2026.
Bring one process you want off your plate.
Make the rules explicit. Test the edge cases. Publish when the result is ready.