29Court · the crew that takes care of things

You bark. It gets handled — with a receipt.

You're the boss. Dillo Flows is the crew: workflows that fetch, decide, branch, and wait for your word — then carry the work out and write every step into the book.

One account for everything 29Court · bring your own provider keys · your flows live in your own space, in your own book.

Fetch a postGET jsonplaceholder.typicode.com/posts/{the one you asked for}

Did it come back?The check: the lookup's status is 200.

When it matchedPull the title, then say it.

Output, verbatim from the run: “Found the post: ‘sunt aut facere repellat provident occaecati excepturi optio reprehenderit’”

When it didn't matchSay what actually happened.

Output, verbatim from the run: “No post came back — the lookup answered status 404.”

The demo waiting in your space when you sign in. Both paths really ran on this engine — end to end.

Example #1 · WUPHF

One message. Every channel at once.

One message, sent every way at once — email, voice call, text, even fax. The flow is pre-rendered: you see every step before anything connects. Each channel starts iced and wakes only when its key is pasted and proven with a live check. This is exactly how a fresh account looks: one channel live, three iced.

The message“The 4pm moved to 5. Bring the deck.” — written once, by the boss.

Email ● Live · provenSent by the house mailer — proven by a real test send.

Voice call IcedBland AI calls and speaks it — wakes when your Bland key validates.

Text IcedTelnyx texts it — wakes when your Telnyx key validates.

Fax IcedSinch faxes it — wakes when your Sinch keys validate. The live send is the one channel not yet proven end-to-end.

The recordEvery channel's result — sent, failed, or iced — written into the run, where you can read it.

A dispatch over iced channels still runs the live ones and reports each iced channel by name. Ice is enforced on the server, in the engine — never faked.

What actually runs

The catalog — every entry executes.

No vapor. If it's listed here, it runs today; if it needs your key, it says so and stays iced until the key proves itself.

FetchCall any API. Your named connections present their sealed secrets by name — keys are never pasted into flows.

Choose a pathBranch on your data: is, contains, greater than, less than.

Ask a personApprovals, questions, tasks, choices — on a signed card. A rejection always takes a comment, enforced by the server.

Shape the textBuild messages from what earlier steps produced.

WaitPark a run and resume it in one tap. It doesn’t wake itself yet — and it says so on its face.

EmailThrough the house mailer. Wakes by proof, not by key — a real test send.

Voice call · Text · FaxBland, Telnyx, Sinch — your accounts, your keys, your bills. Iced until validated.

Rule checkYour rules, checked on the way in and out of steps, every verdict audited.

Dispatch & webhooksWrite to your Dillo board and event feed; anything on the web can knock and start a flow.

Publish as an APIA saved flow becomes an endpoint behind your own scoped key.

Not here, and we won’t fake it: Gmail, Google Sheets and Calendar aren’t connected yet — no real sign-in exists for them today, so they don’t appear as steps or pretend Connect buttons. When they land, they land real.

Text-to-workflow

Say it. It’s drafted.

Describe the workflow in plain words. The house drafter builds a real flow — the same steps, the same engine, nothing drawn on. Every channel in the draft is born iced and wakes only when its key proves live.

Your workflow, in your words

The drafter is a pattern clerk, not a mind reader — it writes its assumptions on the draft, where you can read them before anything runs.

Bring your own keys

Your keys. Your accounts. Your bills.

Nothing master-keyed

Flows never holds a master key to your life. Each provider is your account, connected with your key, sealed the moment you paste it and never shown again — steps ask for it by name alone.

A pasted string proves nothing

Pasting a key doesn't wake a channel. We call the provider, live, and the key has to answer. Iced → validating → live — or failed, with the reason written on the step in plain words and what to do next.

Nothing passes without your word

A flow can stop mid-run and hold at the lock until a person decides — approve, reject with a comment, answer, choose a path. The decision lands in the record with who, when, and what they said.

One door

Hey. Here's your Dillo Flows.

Sign in with the 29Court account you already have. Your space is yours alone: your flows, your keys, your book — and Example #1, WUPHF, pre-rendered and waiting for its first key.