Turn monitoring alerts into a remediation plan
Takes each monitoring alert, gathers recent repository context, drafts a remediation plan, and hands it to the on-call engineer.
Claude Code runs an agent loop over your repositories and can run unattended through routines, on a schedule, an API call or a GitHub event. Whenever is where the job it figured out goes once it repeats: Claude Code writes the workflow, Whenever runs that code on a trigger.
By Whenever team · Updated · Workflow behavior and runtime limits
The steps a session worked out become a workflow module, so each run follows that code instead of planning again.
Classification, summaries and drafts can stay AI steps; everything else runs as code without a model call.
You enter credentials in the browser. Your coding agent never handles a secret.
Claude Code routines draw down subscription usage. Whenever counts whole workflow runs, with optional runtime AI on top.
Subscription usage
Routine runs draw down your plan’s usage
Routines are available on Pro, Max, Team and Enterprise plans, with hourly limits on starting runs.
$39/mo
10,000 runs per month
Find the right plan for youTax exempt for this offering.
At full use of 10,000 included runs, $39 ÷ 10,000 ≈ $0.0039/included run. This is an allowance average, not a per-run tariff, overage price or competitor savings claim. The monthly subscription is still $39 if you use fewer runs; unused allowance, runtime AI usage, moving to a larger plan and external charges change your effective cost.
Routines draw down subscription usage the same way interactive sessions do, and each way of starting a run has an hourly limit. Compare the usage of a representative routine with a workflow’s runs; no competitor dollar price is asserted.
A run is one execution of one workflow, start to finish. AI building and editing are free within weekly usage limits; runs are metered separately.
What changes when you describe the job in plain language and code runs it: to build, to run, and to keep.
Each routine run creates a new Claude Code session that carries out the saved prompt.
AI writes the procedure; published code runs its fixed logic. Optional AI steps can vary, and external data, time or randomness can change results. Fixed logic does not guarantee exactly-once delivery.
Routines draw down subscription usage like interactive sessions, with an hourly limit on each way of starting a run.
Pro includes 10,000 runs per month; see the pricing page for current US dollar prices. AI building and editing are free within weekly usage limits. Published runs are metered separately: the meter counts the whole run, not individual steps. External services and optional model calls can have their own charges.
A routine runs as a full Claude Code cloud session: shell commands, skills committed to the repository and the connectors you include.
Describe the rules you already know; AI writes the procedure. Review the summary and sample results, not necessarily the code. Keep an explicit model step for judgment. Agent platforms may also offer fixed workflows or scripts; compare the mode you actually use.
A routine is a saved Claude Code configuration: a prompt, one or more repositories and a set of connectors.
The TypeScript is yours: read it, edit it, export it, take it with you. Moving it to another runtime can require adapting managed connections, triggers and runtime-specific integrations.
Open any run as a full session to see what Claude did. A green status means the session exited without an infrastructure error, not that the task succeeded.
Each step’s recorded result, a debugger with breakpoints on a saved version, and an email on the first failure. A failed run is not retried or resumed for you.
Claude uses the routine’s selected model on every run.
AI writes the workflow once, with free building subject to weekly AI usage limits. A published procedure runs its steps without a model choosing them. Any model call you explicitly include still runs and has its own cost.
Starter briefs for related jobs, not recorded runs. Connect authorised accounts, confirm trigger and plan requirements, then review and test the workflow before publishing.
Takes each monitoring alert, gathers recent repository context, drafts a remediation plan, and hands it to the on-call engineer.
Weighs recent releases, open incidents and team calendars to suggest the lowest-risk deployment slot and holds it on the calendar.
Celebrates each won deal in Slack with the numbers and a short recap of how it was won.
Checks the search position of every keyword on your list, appends the history to a sheet and reports the moves.
Logs every expense submission in a sheet and alerts a manager in Slack when the amount is over the approval limit.
Pulls open HubSpot deals every Monday, groups them by stage and owner with totals, and shares the write-up in Slack.
No. Claude Code writes and edits the workflow; Whenever runs it.
Official sources captured on the date shown below. These describe published features and billing rules, not independent performance tests. Check the linked documentation for current modes, plans and limits. No competitor dollar price is asserted.
Checked
Ask Claude Code to turn it into a workflow. Whenever hosts, triggers and runs the code you reviewed.
A routine, a scheduled task or a prompt you keep running by hand.
Paste “Turn this task into a Whenever workflow and deploy it. Follow www.whenever.dev/skill.md”.
Enter the credentials, run it once by hand, then publish.