/web local tool
Workflow Builder
Chain typed steps, inspect intermediate values and share recipes without embedding the payload.
Local execution receiptinput path disclosedTool content stays out of MonoTools URLs and API requests.
- Working input
- Browser memory
- Cross-tool handoff
- Session only · 10 min
- URL payload
- Never
- Export
- Explicit action
Verify it: open DevTools Network, clear the log, use the tool, then inspect fetch/XHR requests. Page assets and optional aggregate analytics may use the network; tool input is not included.
Full privacy modelLoading tool...
01
How to use
- 01Pick a preset, import a validated version 1 recipe, or build up to eight typed operations.
- 02Search operations by accepted or output type, or enable automatic recipe branching from the detected input kind.
- 03Paste the payload once, run all steps or run through one step, then inspect each input/output boundary.
- 04Save or share the payload-free recipe; enable full run history only when storing the complete data locally is intentional.
02
FAQ
- How is this different from a normal tool list?
- Most utility sites make you jump between pages. Workflow Builder lets you run several operations in order, similar to a lightweight local recipe system.
- Where are saved runs stored?
- Saved recipes use localStorage but contain steps and bounded settings only. Optional run history also uses localStorage and includes full input and output, so it is disabled by default.
- Can I use this with production payloads?
- Transformations run locally with browser APIs. Keep full run history off for sensitive payloads and still follow your team's data-handling policy.
- How are large inputs handled?
- Inputs above the live-preview threshold wait for an explicit run. Larger jobs execute in a Web Worker with visible progress and a cancel control, within fixed input and output limits.
guides
Guides
03