Whenever

npx add-mcp 'https://mcp.whenever.dev'

Whenever

Whenever runs business-process automation as code: AI writes a TypeScript workflow once, and Whenever schedules and executes that same code deterministically on every run: no node graph, and nothing asks a model what to do next. Metered per run; free AI building and editing have weekly usage limits.

AI workflow automation. Runs the same way, every time.

AI is brilliant at building. Wasteful at repeating.

Describe it in plain words. Whenever writes real code you own and runs it across any of your tools. No coding needed, and no ceiling when you want one.

Used by teams behind Wix, Symphony, Wixel, Base44, Tabless and Brik.

Your agent is still thinking. Whenever is done.

An agent stops to reason through every invoice, so work piles up behind it, and now and then it gets one wrong. Whenever runs your workflow as code. The only AI step is the one you add, like writing the vendor email.

• Same result, every run. For invoices, refunds and payouts, a 1% error rate is too much. Whenever makes the same decision every time.
• Faster. Whenever runs your workflow in milliseconds. Nothing waits for a model to think it through again.
• Cheaper. Whenever uses AI once, to write your workflow. After that, every run is almost free.
• AI where it helps. Need a reply written, a PDF read or a judgment call? Add an AI step in Whenever, only where you want it.

Any API, even the one nobody supports.*

1,402 integrations in the catalogue. Not in the list? Name the service and Whenever reads its API documentation, tells you which pages it used, and writes the integration. Nothing published? Paste the docs you do have.

* The API must be reachable from Whenever’s hosted runtime. You still need the provider’s required credentials, permissions and plan; private-network-only services are not automatically accessible.

Browse all integrations

Look inside the black box.

Node builders hide complex logic in Code nodes that nobody can read. Whenever writes the whole workflow as code, so every step reads in plain words.

Your agent works in chat. Now make it run on its own.

Paste the prompt behind your assistant’s scheduled task, or send it from your coding agent through our MCP server. Whenever makes it run on its own.

MCP server: https://mcp.whenever.dev — MCP Setup Guide

Ask your coding agent:

Every weekday at 8am, find yesterday’s Stripe refunds over $200 and post a summary to #finance with each customer and the reason. Use https://www.whenever.dev/skill.md

Start with a workflow brief

Pick a starting point, connect your accounts and review what Whenever builds before publishing.

Browse all templates

Free to start. Pay per run.

Start with one free workflow, no credit card. Upgrade when you need more workflows or runs. No per-step or per-item counting: one run is one run, however many steps it has.

• Hobby: $0/mo. 100 runs per month. One active workflow, no credit card.
• Pro: 10,000 runs per month. Find the right plan for you

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.

Or bring one over and stop tracing it node by node

Describe the automation you already have and Whenever rebuilds it as one file you read top to bottom instead of a canvas you follow with your finger, testable before it goes live.

• Coming from n8n: Describe what your node graph does and Whenever rebuilds it as a module you read top to bottom.
• Coming from Zapier: Describe your Zap’s triggers and actions and get a workflow you can edit, test and keep.

The things people ask first

Do I have to write code?

No. You describe what you want in plain language and Whenever writes the workflow. The code is there when you want it, to read, to review, or to edit, and ignoring it is a perfectly normal way to use Whenever.

What does "workflow-as-code" mean?

A language model writes your automation once, as a typed TypeScript module. Every run after that executes that code: the same input follows the same rules. If you add an AI step, its output is not guaranteed to be the same, and it incurs runtime AI usage when it runs.

If I add an AI step, does every run still give the same result?

Not for that step. Everything around it runs the same way every time, but an AI step asks a model, and a model can word its answer differently, or decide differently, from one run to the next. The rest of the workflow can check that answer before anything acts on it. An AI step also draws on your plan’s AI allowance on the runs where it happens.

What happens when an API changes?

Nothing changes shape under you: the workflow keeps running the code it was given. When a call starts failing, your run history shows which step broke, and you can ask Whenever to rewrite that step against the new API.

How do triggers work?

A workflow runs on a webhook, on a cron schedule, or on demand. Credentials are managed for you and there is nothing to host, so there is no server to babysit between runs.

What happens if a run fails? Are there retries and alerts?

The run stays in your run history with the step that failed, its error, and what the run returned, so you can see where it broke rather than guessing from a log line. Whenever does not re-run a failed run for you, and it does not send failure alerts on its own. If you want a retry, or a Slack or email message when something fails, ask Whenever to write it into the workflow.

Can I see the history of past runs?

Yes. Every workflow has a run history: when each run happened, what started it, which version ran, and whether it succeeded. Open a run to see each step, how long it took, where it failed and what it returned. Runs and their steps are kept for 90 days.

Are my workflows versioned? Can I roll back?

Every saved change becomes a new numbered version, and your live workflow keeps running the version you turned on until you turn on the new one. Each run shows which version it used. There is no one-click rollback yet: to go back, describe the change you want undone and Whenever edits the workflow again.

How long is run history kept?

Run history is kept for 7 days on Hobby and 30 days on Pro. Those are the retention periods listed on the pricing page.

Can I export my workflows?

Yes. A workflow is a TypeScript module, not a diagram locked inside a database, so you can take it with you.

Who builds Whenever?

Wix.com Ltd, the Nasdaq-listed company (ticker WIX). Whenever is one of its products, not a site built on the Wix website platform.

Agents should build your automations, not be them

Describe your first workflow in plain words. One stays live for free, no credit card.