Automation that never holds the key.

Build it on a canvas. Every step calls your APIs with a secret KnoxCall holds; the key is added at the call and never pasted in.

Start for free Read the docs

The key stays here.

A step names a secret. It never carries one.

The same custody path the proxy uses; workflows are a consumer of it, not a second copy of it.

Secrets by referenceA key pasted into a field is refused before it is stored, so a definition anyone can read holds none.
Egress through the same doorA step calling any URL goes through the proxy's pinned path, the one that refuses private addresses.
Mail you are allowed to sendOn the platform's credential, only from a domain you have proven in DNS.

Runs that outlive the process.

Waiting is a state, not a held thread. Failure is a path you draw.

A broken workflow is disabled after five failures in a row, so it stops burning quota instead of failing all week.

Wait for an event, or a personDays if needed, holding no worker, inside a loop too. A restart changes nothing about where it resumes.
Retry per step, fail on a path you drewBounded attempts, an output only failures take, a workflow that runs when this one fails.
Live and test never mixTest runs use test credentials and test data, with no fallback to live.

Debug it where you built it.

A finished run loads back onto the canvas it was drawn on, each step showing what it received and what it produced.

  • Live status on the nodesStreamed rather than polled.
  • Retry from the step that failedKeep everything already done.
  • The data in front of youSample data per step, a variable picker, an expression preview.
  • Test a single stepBefore the whole workflow.
  • Call another workflowDepth and fan-out are bounded.
  • Sixteen apps, any APISlack, Stripe, GitHub, Notion, Jira and eleven more; anything else is an HTTP step.

Store. Proxy. Revoke.

Free for seven days. No card. Your first call in minutes.

Start for free Talk to us
All systems operational