Back to guides

WoDeTool pipelines: stop redoing the same three clicks

Chain tools so each step feeds the next. Config stays in localStorage. Three examples you can steal.

By WGinit · June 12, 2026

What a pipeline is

You line up tools in order. Output of one becomes input of the next. Saved in localStorage; no account.

Good for weekly chores: Base64 decode → JSON format → copy, or URL decode → parse query params.

Example: webhook debug

Payload arrives Base64-wrapped. Decode to a JSON string, format it, and if there’s a JWT inside, send that token to JWT Decoder (add it as step 3 if you want).

Save as “Webhook debug”. Next ping, one click runs the chain.

Example: check data before release

After CSV → JSON: format for syntax, Diff against a golden file, fix the source in JSON↔CSV if something’s off.

Run it before every data drop. Catches “looks fine but a field vanished” earlier than production does.

Clipboard detection and the extension

Smart Clipboard sniffs pasted JSON, Base64, JWT, and suggests a starting tool. Think of it as the front door to a pipeline.

The Chrome extension opens wodetool.com from a selection with input filled. Extension for the first jump; pipeline for the fixed multi-step job.

Related tools

Related guides