Crank

What it does

• Create and activate a flow that passes events from one app to another over the web
• Show each run's exact input and destination before anyone approves or rejects it
• Record the decision and the delivery result for every run
• Replay a failed delivery once, so the receiving app records it only once
• Take events from your sending app with a limited credential for a single flow
• Let an assistant prepare flows and runs, but never approve them
• Import a supported n8n workflow export with a preview, journal and undo
• Back up and restore your workflows, and erase a completed run
• Try it with an included local receiving app, the Operations inbox

What it promises

• A person approves a run's exact body and destination before anything is delivered; an assistant can prepare but cannot approve, reject, replay, import, export or erase.
• Sending the same event ID and body again returns the existing run, and changed input under an event ID is refused.
• A failed delivery can be replayed once only, using the original approved body and the same idempotency key.
• An n8n import is previewed and approved first, journalled, and can be undone only while the imported draft is unused.
• Backups restore only into an empty installation and leave out owners, sessions and tokens.
• Erasing a run blocks an older backup from restoring its data, though the receiving app keeps the effect it already recorded.
• Crank holds no third-party credentials, makes no live calls to other services on its own and has no scheduling; destinations must support the documented idempotency rule.

Move in from

• n8n workflow export (supported subset)

Run it yourself

Install the command once, then clone a product and start it.

$ npx -y @runeditrun/rer cli install
$ git clone https://github.com/just-every/run-crank
$ cd run-crank && rer dev

No npm? curl -fsSL https://runeditrun.com/install.sh | sh installs the same command.