Skip to content

Power Automate alternative: describe the flow, skip the designer

Power Automate builds cloud flows in a designer, with Copilot to draft one from a prompt; Whenever turns your description into a workflow you supervise through summaries and sample outputs.

By Whenever team · Updated · Workflow behavior and runtime limits

What you get on Whenever

  • Described, not configured

    Describe the job in plain words and review the procedure and sample outputs. Power Automate’s Copilot also drafts a flow from a prompt, then opens it in the designer.

  • One run, however many actions

    The meter counts a whole workflow run within its call budget, not each action or each person who uses it; a different unit is not by itself a lower bill.

  • Logic you can read and take with you

    Whenever produces a readable TypeScript workflow you can export. Power Automate exports solution-aware flows as JSON files inside a solution zip file.

A concrete decision

Illustrative scenarios, not customer results or recorded runs.

  • Reconcile a batch and report only what failed

    Read new orders, match each to its payment and report only the mismatches. Price that batch on each plan, including every action, retry and AI step.

Licenses per user or flow, or one run per workflow.

Power Automate licenses users, flows and bots with daily action limits; Whenever counts whole workflow runs. The two units count different work, so compare an actual workload and plan terms.

Power Automate

Per-user and per-flow licenses

Users, flows or bots, with daily action limits

Premium is a paid user license; Process and Hosted Process are capacity licenses allocated to a cloud flow, machine or hosted machine. Each carries a daily action limit, and premium connectors need one of them.

Whenever

$39/mo

10,000 runs per month

Find the right plan for you

Tax 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.

Do not divide a daily action limit by the number of flows. Which people need a license, which flows need their own, and which connectors are premium all affect the bill. See Microsoft’s pricing page for current figures; 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.

A closer look

What changes when you describe the job in plain language and code runs it: to build, to run, and to keep.

Repeatable execution logic

Power Automate

A cloud flow runs the trigger and actions you configure in the designer or that Copilot suggests from your prompt. Generative actions, in preview, instead let the AI choose the set of actions from your stated intent.

Whenever

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.

Runs per dollar

Power Automate

Microsoft licenses Power Automate per user with Premium, or per cloud flow, machine or hosted machine with Process and Hosted Process, each with a daily action limit. The Free license is limited to standard connectors; premium connectors need one of the paid licenses.

Whenever

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.

What you can express

Power Automate

Cloud flows connect apps through connectors and start automatically, instantly or on a schedule; desktop flows automate desktop and web applications with drag-and-drop or recorded actions. Copilot builds and edits a cloud flow from natural language, so describing a flow is not the distinction.

Whenever

Describe the job in plain language: match payments to orders, fetch every page of contacts, or alert only on unseen reviews. AI writes the procedure; you supervise its rules and results, and reading code is optional. API access still needs suitable permissions and a service reachable from the hosted runtime.

Export and portability

Power Automate

Solution-aware flows export in a solution zip file in which each workflow is a JSON file. Microsoft says the solution should contain the connection references, environment variables and tables the flow uses, and managed solutions cannot be exported.

Whenever

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.

Debugging a failed run

Power Automate

The run history view shows each run’s start, duration and status for 28 days, and a failed action’s inputs can be inspected. Repair-tips emails go to flow owners when a cloud flow fails, and Copilot can summarise an error in the new designer.

Whenever

Review the execution log, summary and sample outputs; inspect TypeScript if useful. Power Automate also documents run history and failure emails, so debugging availability is not the distinction.

Where the AI cost lands

Power Automate

Not every flow needs AI. AI Builder usage is metered in service credits that different scenarios consume at different rates; Premium, Process and Hosted Process licenses each include a monthly credit allowance, and add-ons sell more.

Whenever

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.

Cloud flows and desktop flows

Power Automate

Cloud flows run on triggers in Microsoft’s cloud. Desktop flows are Power Automate’s robotic process automation: they run on a registered machine or a Microsoft-hosted machine, attended or unattended, and each run mode is licensed separately.

Whenever

Whenever runs hosted workflows that call integrations and documented APIs. Work that exists only on a desktop application’s screen stays a desktop-flow job.

When to keep Power Automate

Power Automate

Keep Power Automate when your team works inside Microsoft 365 or Dynamics 365, whose licenses include a limited set of its capabilities, or when the job needs a desktop flow. Moving a simple working flow may buy very little.

Whenever

Consider Whenever for logic that is easier to understand as a procedure, or when you prefer a whole-run allowance to per-user licenses and daily action limits.

Email and spreadsheet workflows to start from

Starter briefs for related jobs, not recorded runs. Connect authorised accounts, confirm trigger and plan requirements, then review and test the workflow before publishing.

Browse all templates

Questions people ask before switching

Where is the Power Automate portal?

make.powerautomate.com is Microsoft’s Power Automate portal: its troubleshooting guide has you sign in there to open a flow’s run history. Whenever’s builder is at app.whenever.dev.

What does a Power Automate Premium license cost, and what is in it?

Microsoft prices Premium per user per month, paid yearly, and lists the current figure on its pricing page. It is a paid user license with standard, premium and custom connectors, attended desktop flows and a daily action limit. Whenever Pro includes 10,000 runs per month; see the pricing page for current prices.

Can Whenever replace desktop flows?

Desktop flows automate desktop and web applications with drag-and-drop or recorded actions on a machine. Whenever runs hosted workflows against integrations and documented APIs, so it replaces cloud flows that connect services, not a robot that drives a desktop application.

Can I import my Power Automate flows?

Whenever does not import solution files. Describe what the flow does, or hand the exported flow to your coding agent as a specification, then test the result before switching.

Sources and scope

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

Start with one cloud flow.

Describe one cloud flow and Whenever writes it as a procedure you can read top to bottom; the rest can stay in Power Automate.

  1. Export the solution and note the trigger

    Export the solution zip, or write down each action; note the trigger, schedule and the accounts each connector used.

  2. Review the translated procedure

    Use the flow as a specification, review the rules and sample results, then reconnect services in Setup.

  3. Compare outputs before switching

    Run both on safe test records, then turn the cloud flow off before publishing.

Start for freeNo credit card requiredAI building has weekly usage limits.