Move your n8n workflows to Whisk
n8n counts the way Whisk does: one run of a workflow is one execution, however many steps it has. So moving to Whisk isn't mainly about the price per run. It's about who looks after the server, and about what the automation can grow into once it's part of an app.
If you run n8n yourself
A lot of businesses run n8n on their own server because it's free to use that way. Someone set it up, often a contractor or the one technical person in the office. That server now runs the business's automations, and someone has to keep it going:
- updating n8n, and the operating system under it, when security fixes come out
- backing up the workflows and the credentials, and checking a backup actually restores
- noticing when the disk fills up or the server restarts and the workflows don't come back
- keeping the database n8n uses healthy
That's fine while the person who set it up is around. It's a risk when they aren't.
On Whisk, there's no server to look after. Updates, backups and restarts are Whisk's job, and the workflows run as part of your app.
If you use n8n Cloud
n8n Cloud's Starter plan is €20 a month for 2,500 executions, and Pro is €50 a month for 10,000. A workflow that runs on every order or every email can use 2,500 executions in a week at a busy distributor.
On Whisk, every business runs one app free with 10,000 runs a month, and Starter is $49 a month for 10 apps and 100,000 runs. Past the allowance, new runs wait rather than being charged.
Prices are from n8n's and Whisk's pricing pages in October 2026.
What the app can do that the workflow can't
A workflow passes data from one system to another. An app can also keep its own data and show screens.
Take a business that sells fasteners and fixings to builders. Its n8n workflow copies each new web order into the accounting system. As part of an app, the same workflow can also:
- keep a list of orders waiting on stock, which the counter staff can open in a browser
- hold an order over the customer's credit limit until the accounts person approves it, and carry on when they do
- show the warehouse a picking list for each delivery run
Each of these is a few more lines in the prompt, not another tool to pay for.
Moving a workflow
In n8n, open the workflow, open the menu and download it. You get a JSON file with every node and connection. Credentials aren't included, which is what you want.
Give the file to an AI coding assistant like Claude Code, Cursor or Codex, with this prompt:
Read https://whisk.run/skill and follow it. The attached file is an n8n workflow. Rebuild it as a Whisk app with a Whisk workflow that does the same thing, one workflow step per node. Replace the n8n webhook and schedule triggers with Whisk webhooks and schedules. Turn any Code nodes into ordinary functions. Ask me for the access keys you need through Whisk's secrets. Deploy it to Whisk when it passes whisk doctor.
The AI tells you the new webhook address. Point the other system at it, and run the two side by side until the results match. Then switch the n8n workflow off.