Bring every lead source into one CRM record
Collects new leads from Typeform and a Google Sheets tab and creates or updates a single HubSpot contact with its original source.
Build, deploy, and run deterministic flows, AI steps, and full agents in one place.
No credit card required. Deploy from Claude Code, Codex, or Cursor.
Used by teams behind
1 of 6Describe it
Celebrates each won deal in Slack with the numbers and a short recap of how it was won.
Publishes due rows from your Instagram calendar on the cadence you choose and writes each post link back.
Adds each survey response to Google Sheets within minutes and emails the owner when the score falls below your threshold.
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.
Ask Claude Code, Codex or Cursor to turn the task your agent repeats into a workflow. It writes the code, saves a draft and deploys it to Whenever through our MCP server. You connect the accounts and decide when it goes live.
mcp.whenever.dev
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
Created refund-summary. Runs every weekday at 8am.
Every weekday at 8:00
List yesterday’s refunds
Keep refunds over $200
Post a summary to #finance
On · runs weekdays at 8:00
#finance
Already have it somewhere else? An n8n workflow, a Claude task or a ChatGPT scheduled task: give it to your coding agent with our skill, and it reshapes it into a Whenever workflow and deploys it.
Turn this into a Whenever workflow and deploy it. Follow www.whenever.dev/skill.md <paste your n8n workflow JSON, Claude task or ChatGPT task here>
AI is brilliant at building. Wasteful at repeating.
Turn your agents into code: same result, a fraction of the cost, and the same steps every time.
For invoices, refunds and payouts, a 1% error rate is too much. Whenever makes the same decision every time. Whenever runs your workflow in milliseconds. Nothing waits for a model to think it through again.
Whenever uses AI once, to write your workflow. After that, every run is almost free.
Need a reply written, a PDF read or a judgment call? Add an AI step in Whenever, only where you need it.
*For the steps that run as code. Add an AI step and that step can vary, and uses your plan’s AI spend in runs.
Pick a starting point, connect your accounts and review what Whenever builds before publishing.
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.
1,402 integrations in the catalogue. Not listed? Name it, and Whenever reads the docs and writes the integration.
- 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. The CRM your dental clinic runs on
Not in the cataloguedocs.dentadesk.io A warehouse system from 2011
Not in the cataloguepasted PDF manual Your team’s own admin API
Not in the catalogueopenapi.json Triggers, credentials, run history and versions are built in. There's no server for you to run.
Webhooks, schedules, app events and on-demand runs.
You enter them once in the browser. Nothing to host, and your coding agent never sees a secret.
Every step’s input, output and error, kept 7 days on Hobby and 30 on Pro.
Every save is a version. Production keeps running the one you turned on until you switch, and any version exports as TypeScript you own.
While you build, the builder reads the logs and helps you fix it. In production, you get an email when a run fails, and fix it in the app or from your coding agent.
For the workflows your canvas can’t hold
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.
Every hour
Get new orders
Skip test orders and staff accounts
Add up line items and tax
Apply EU VAT for EU customers
If the order is over $1,000 Yes
Post it to #finance
Otherwise, continue to Sheets
Add a row to “Orders”
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.
Wix.com Ltd, the Nasdaq-listed company (ticker WIX). Whenever is one of its products, not a site built on the Wix website platform.
Follow the setup on whenever.dev/mcp: it shows how to connect Claude Code, Codex or Cursor and deploy your first workflow.
Yes, as a step in a workflow: an agent loop with the tools you give it and a capped number of turns, within a run of up to an hour. It sits next to fixed steps and single AI calls in the same workflow. Whenever is not an always-on chat agent.
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.
AI writes your automation once, as a typed TypeScript module, and every run executes that code. A workflow can be fixed steps only, call a model in one step where judgment is needed, or run an agent loop inside a step. The fixed steps follow the same rules on every run; AI steps and agent loops can vary between runs and draw on your plan’s included AI spend in runs.
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.
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.
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.
A failed run is not retried automatically. While you build or test, the builder shows the run’s logs and helps you fix the workflow. In production, you get an email when an automated run fails, at most one per workflow per 24 hours, and you fix it from the logs, in the app or with your coding agent.
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 7 days on Hobby and 30 days on Pro.
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.
Run history is kept for 7 days on Hobby and 30 days on Pro. Those are the retention periods listed on the pricing page.
Yes. A workflow is a TypeScript module, not a diagram locked inside a database, so you can take it with you.
Deploy your first workflow from your coding agent, or describe it in plain words. One stays live for free, no credit card.