We're at AccessAbilities expo in Dubai on 19 Oct! Come join us! Private beta · Concert Tickets are out 🎟️ What the hell is a kilowatt-hour?
Nodes made of nodes

A workflow that becomes a node.

Declare a Contract inside any flow and it turns into a node you can place anywhere. Its fields, its secrets and its buttons are small nodes inside it. Open it, and the whole flow is there.

  1. 01 Node ContractSend invoice Declares the node: its name, its category, its icon.
  2. 02 Node InputOrder An input port. Data arrives here.
  3. 03 Node OutputInvoice An output port. Data leaves here.
  4. 04 Node Supply PortTools A callback port. During a run the node asks for something, and the handler wired to the port answers.
  5. 05 Node FieldCustomer email A setting on the node's card.
  6. 06 Node FieldDue in days A setting on the node's card.
  7. 07 Node SecretBilling API key A setting that is stored encrypted and never shown again.
  8. 08 Node ButtonSet up A button on the node that runs part of the flow inside.
  9. 09 The requestCreate invoice The work itself. It stays inside, out of sight.
  10. 10 Into the node The panel is the inside of the node. It closes, and one node is left.

Change a name on any small node; it comes through at the end.

For the engineers

If you have used automation tools before, you know a node as something the vendor writes and you consume. Here a node is something you write, on the same canvas, with the same nodes, in the same afternoon. The library is not a wall between you and the product.

Nothing is opaque

Opening a composed node reveals its canvas exactly as if it were the top level. Every level is inspectable, every value visible.

Reuse without copy-paste

Place the node in as many flows as you like. Change the flow behind it and publish a new version; the flows that use it pick it up from the registry.

Integrations are flows too

An integration for a vendor is a flow of HTTP requests with a Contract in front. Build it once, export it, install it in any space.

Wizards for the hard setups

A Node Wizard walks a person through a multi-step setup, redirects and callbacks included, so a node can ask for consent and keys the proper way.

The parts

Eleven small nodes make a node.

Each thing a node shows the outside world is contributed by one of these, placed inside the flow behind it.

A flow on the canvas that declares a Node Contract, with Node Field and Node Output nodes wired to an HTTP Request. A flow on the canvas that declares a Node Contract, with Node Field and Node Output nodes wired to an HTTP Request.
Node Contract Declares the node: its name, its category, its icon.
Node Input An input port. Data arrives here.
Node Output An output port. Data leaves here.
Node Field A setting on the node's card.
Node Secret A setting that is stored encrypted and never shown again.
Node Button A button on the node that runs part of the flow inside.
Node Wizard A multi-step setup, with redirects and callbacks.
Wizard Step One screen of a wizard.
Node Context A right-click action on the node, run by the flow inside it.
Node Supply Port A callback port. During a run the node asks for something, and the handler wired to the port answers.
Augment Extra fields for the nodes wired to a supply port, shown only in that context.

Ready when you are.

Join the waitlist for a Concert Ticket, or see how it works right now.

Join the waitlist See how it works