Build

Workflow Builder

Chain steps on a canvas into small reusable checks: inputs, HTTP and DNS lookups, conditions with true and false branches, JSON and text tools, and a result.

Browser and server
Free to run

Open the tool

You enter: Steps and connections; when you run it, the values of the input steps.
You get: The value of the Return Data step, a log of every step with its time, and the run kept in the run history.
A good result: Every step ok in the log and the result you expected.

On this page

What it is for
What you enter
How it works
Reading the results
Example
Limits and gotchas

#What it is for

Turn a check you repeat by hand (look up a CNAME, call a URL, pull a field out of a webhook body) into a workflow you run with one click.

#What you enter

The page opens on your library of workflows: search them, start a new one, start from a template, duplicate, import or delete. Opening one shows the canvas with a step palette, the inspector for the selected step and the run panel. Nineteen step types in seven groups:

Inputs: Text Input, JSON Input: a default value the person running it can change.
Web & DNS: HTTP Request (GET or HEAD), DNS Lookup (A, AAAA, CNAME, MX, NS, TXT).
Logic: Condition: truthy, falsy, equals, contains, empty; with a true and a false way out.
JSON & numbers: Template, Transform JSON, Pick JSON Value, Build JSON, Math.
Text: Text Value, Combine Text, Replace Text, Encode / Decode, URL Parts, Find Emails.
Output: Return Data: the result of the run.
Utilities: Logger, Delay.

Steps write named variables; later steps read them as {{variable}}. The inspector checks each field as you type and says which variable is missing.

#How it works

A run happens in your browser. Steps run in the order of their connections; loops are refused. A Condition sends the run down its true or its false branch, and the steps on the other branch are skipped. A step can be switched off or carry a note. The first error stops the run. Workflows are saved on the server as you edit, so they are there next time.

Seven templates to start from: Tracking Domain Checker, Public API Status Check, Manual Response Formatter, Email Address Finder, URL Breakdown, Slug Maker and Webhook Field Picker.

On the canvas: drag to connect, select several steps to move, copy or duplicate them, auto-arrange, and find your way with the minimap. Undo and redo cover every change; keyboard shortcuts are listed in the editor (for example Ctrl+S to save, Ctrl+Enter to run).

#Reading the results

The log lists every step as ok, error or skip with its time in milliseconds. The output panel shows what Return Data returned, or the error and all variables at that moment. Past runs stay in the run history of the workflow.

Saved versions (up to 8) let you go back to an earlier state. Export JSON saves a copy you can import again, into a new workflow or merged into an open one.

#Example

The Tracking Domain Checker template: enter track.example.com, it looks up the CNAME, checks a condition and calls the domain over HTTPS.

A good result

{"dns_ok": true, "cname_target": "eu.v2.spgo.io", "https_status": 200}

#Limits and gotchas

At most 40 nodes and 70 connections per workflow, 20,000 characters per setting.
HTTP Request does GET and HEAD only, waits up to 15 seconds, does not follow redirects and refuses private addresses. Responses are cut at 200,000 characters.
Delay waits at most 3 seconds. DNS Lookup uses the first answer only.
Saved workflows: 3 as a guest, 8 with an account, 20 with a verified email.