// workflows/new

Build a workflow.

Pick the capabilities, say where each field gets its value, and run it before you save it. Building one costs nothing: what an account changes is where it is kept. Every rule the server enforces is checked here as you type, so saving cannot fail for a reason you could not see.

This is the "Read an encoded payload" example with its sample values filled in. It is not saved yet: change anything, test it, then save it as your own.
· What it is called
· What it asks for

Declare a value here when it changes from run to run. Steps read it by its key. Anything that never changes belongs in the step itself as a fixed value, not here. A workflow may declare up to 10 inputs, and none at all is fine.

· What it does

Steps run top to bottom, one after another. A step can use a fixed value, one of the inputs above, or the output of any step above it. Up to 12 steps.

Every one of its 2 steps is pure computation, so a test run in the builder happens on your own machine and costs nothing. Your input is not sent to us for it.

Run from your saved workflows, from your code or from an assistant, the work happens on our machines and is metered: 2 credits, one call per step across 2 steps.

Adding a step that needs our side, meaning anything touching a key we hold, a database, the network or a file, would move the whole run onto our servers and it would be charged there too.

· Step 1 of 2 · 1 credit

Base64 Encode/Decode

Encode text to Base64 or decode Base64 back to text, byte for byte, with UTF-8 handled correctly.

Reads: input from input "payload" · action is fixed

Gives back:output textaction text, usable by every step below as “Output of an earlier step”
· Where each field comes from
input (required)Text (String)

The text to encode, or the Base64 string to decode. Example: ToolForte

action (optional)Text (String)

"encode" (default) or "decode". Example: encode

What this step gives back
{
  "output": "VG9vbEZvcnRl",
  "action": "encode"
}

A later step reading this one can take the whole object, or a path into it such as output.

· Step 2 of 2 · 1 credit

JSON Formatter

Pretty-print, minify or validate a JSON string with a real parser, reporting the line and column of any syntax error.

Reads: json from "output" of Decode the payload · action is fixed · indent is fixed

Gives back:output textvalid yes/no
· Where each field comes from
json (required)Text (String)

The JSON text to work on, as a string, not an object. Example: {"name":"ToolForte","version":1}

Takes text from “Decode the payload”, for example VG9vbEZvcnRl.
action (optional)Text (String)

What to do with it: "format" (default), "minify" or "validate". Example: format

indent (optional)Number

Spaces per level when formatting. Defaults to 2. Example: 2

What this step gives back
{
  "output": "{\n  \"name\": \"ToolForte\",\n  \"version\": 1\n}",
  "valid": true
}

A later step reading this one can take the whole object, or a path into it such as output.

· Test it before you save

This runs the workflow exactly as written, without saving it. It uses the real capabilities, so what you see is what a later run will do. Inputs are prefilled from the examples you gave them.

Stays on your device

This runs in your browser. What you put in is never sent to ToolForte, so we could not read it if we wanted to.

One exception, so the sentence above stays true: when a run finishes here we record that it happened, which ready made workflow it came from if it came from one, how many steps it had and how long it took. Never what you put in, never what came back, and never anything written into the steps themselves. It is how we can tell which tools are worth keeping.

Runs in your browser. No credits, nothing sent to us.
Saved in this browser

This is saved by your browser on this device. It is not sent to ToolForte, so it is not on your other devices and we cannot recover it for you.

Clearing your browser data removes it, and so does the delete button here.

Leave without savingUnsaved changes.