Text workflow builder

MULTIVERTO / Text workflows

How the workflow works

Each step receives the complete result of the step before it. Start with one or more text tools, arrange them in the order the data actually needs, and run the sequence against your input. The preview shows what each transformation produced. A shortened preview still passes its full, unshortened value to the following step. This makes the page useful for diagnosing mixed encodings instead of guessing where a value became invalid.

Order matters. To read text that was first HTML-escaped and then URL-encoded, URL decoding must happen before HTML decoding. The ready-made web-value workflow demonstrates that order with a short example. For Base64-wrapped JSON, decode Base64 before formatting JSON. Reversing either sequence can cause a valid operation to fail because its input is still in the wrong format.

A failed step is identified by its position and tool name. Earlier previews remain visible, so you can inspect the last valid value and correct the input or rearrange tools. Encoding and hashing are different operations: a hash cannot be reversed to recover its source. A recipe may still include a hash at the end when you need a fingerprint, but a decoding step after hashing will not restore the original text.

Saved recipes stay in this browser and contain a name plus the list of tool IDs. Loading a recipe never restores old input or output. The share link also lists only tool IDs in the URL fragment, with no input, intermediate values or results. Anyone opening the link must supply their own input. For sensitive text, review every selected operation and avoid pasting data into untrusted websites or browser extensions.

Use the move controls when a workflow produces an unexpected value; you do not need to delete and rebuild the entire sequence. For example, JSON formatting needs valid JSON text, so place any Base64 or URL decoding before it. If a decoding step reports malformed input, inspect the previous preview for incomplete escape sequences, invalid characters or missing padding. The page accepts up to eight steps and limits each intermediate value to one million characters to protect browser responsiveness. Large transformations can still take time on a slower device. You can clear the input and results without deleting your named recipes, or delete a saved recipe separately. When you copy a share link, check its fragment: it should list short tool IDs only. If a tool is removed in a future version, an old link is rejected rather than silently substituting a different operation.