Excel Workflow Automation — Without VBA or Macros
When people say "automate Excel," they usually reach for VBA macros — and then they hit a wall. The macro breaks when a column moves. Nobody on the team can read it. It only works on the one workbook it was written for. And the moment the person who wrote it leaves, the "automation" becomes a black box no one dares touch.
For the most common job — cleaning, merging, and reshaping the same files on a schedule — there's a simpler kind of automation that needs no code at all.
Why VBA and macros are the wrong tool for most teams
- They're brittle. Hard-coded cell ranges and column positions break the instant the source layout shifts.
- They need a coder. Editing VBA is a developer skill; the analyst who owns the report often can't maintain it.
- They're trapped. A macro lives inside one workbook — not a portable thing you can share or reuse across files.
- They're opaque. "Don't touch the macro" is how a one-time automation becomes permanent technical debt.
What spreadsheet "workflow automation" actually means
The repetitive part of Excel work isn't the thinking — it's the redoing. You already know the steps: dedupe, fix the dates, merge in the lookup table, drop the junk rows, total it up. Automation just means recording that sequence once so you never hand-perform it again. You build a recipe — an ordered set of plain-language steps — and replay it on each new file.
| VBA / Macros | Kramata recipe | |
|---|---|---|
| Repeatable | Yes | Yes |
| Survives columns moving | No | Yes |
| Editable by non-coders | No | Yes |
| Portable / shareable file | No | Yes (.json) |
| Runs across a whole folder | Hard | Yes (batch) |
| Fully local, nothing uploaded | Yes | Yes |
What you can automate this way
- Standardize messy exports — dates, casing, whitespace, types — the same way on every file.
- Merge in reference data from another file (a reproducible VLOOKUP / XLOOKUP) without formulas.
- Pivot, unpivot, split and combine columns, and flag rows that fail your checks.
- Run the whole thing across a folder of files at once.
How to set it up
- Open one representative file.
- Add your steps in plain language; watch the preview update so you can trust each one.
- Save it as a recipe.
- Every future file: load, apply, export. No VBA, no rebuilding, no broken references.
Related guides
Spreadsheet recipes: build once, reuse forever · Automate monthly Excel reports · A simple Power Query alternative
FAQ
Can I automate Excel without VBA? Yes. For the common case — cleaning, merging and reshaping recurring files — you build the whole workflow in plain language as a reusable recipe and re-run it in one click, no VBA or macros.
Why not just use a macro? Macros break when columns move, need someone who can read VBA, and live trapped inside one workbook. A plain-language recipe is portable, doesn't break on column changes, and anyone can run it.
Does it run on a schedule by itself? Kramata is a manual one-click run, not an unattended server job — by design, so your data stays local. The automation is in not rebuilding the steps.
Is it really code-free? Yes. Every step is plain language — no VBA, no M, no formulas. Your files never leave your computer.