Skip to content
Book a demo Start building

Put a flow builder inside your product.

Your customers build their own automations without leaving your app. You choose the integrations they see, the branding around it, and what each one can run.

Talk to usRead the docs
Live Test
WebhookNew submissionTrigger
Hot lead
SlackNotify sales
Just browsing
HubSpotAdd to nurture

Your users never sign up twice

Your app signs them in, and their workspace is created the first time they open it.

You decide what they see

Show only the integrations you sell, hide what you don't need, run it on your subdomain.

Every customer stays separate

One project each, with its own automations, connections, history and usage limits.

What the SDK gives you.

Sign Them In Once

Your backend signs a token, and the account exists.

The Builder In Your Page

One configure() call and the builder appears.

Accounts Already Connected

Connect their accounts for them, or let them.

Hide What You Don't Need

Sidebar, folders, search, import and export.

Your Domain, Your Font

Your own subdomain and font, light or dark.

Only The Apps You Sell

Build one list of integrations and reuse it.

Limits Per Customer

Set each customer's task and credit ceiling.

Ready For Their AI

An assistant can run their automations.

Common questions.

They do not log in twice. You sign a short-lived RS256 token in your backend carrying your own ids, and the SDK exchanges it for a session. If the user and project exist, the token signs them in; if not, both are created. The role is in the same token, so the same person can be an editor in one workspace and a viewer in another.

The URL is a subdomain you own, and you pass your own font and light or dark mode. The sidebar, folder tree, flow name, search, import and export, and the tables interface are each a flag you can switch off, and navigation can be a single home button that calls your own router. The formula editor links to your documentation rather than ours.

Yes, with one claim in the token rather than a separate deployment. You build a named set in the platform admin, choosing the integrations and even which of their actions and triggers are visible. Whichever set the token names is the catalog that customer sees.

Not if you already hold the credential. Create the connection over the API when you provision the project, and the app is authorized before the customer opens the builder. When you do want them to connect something, calling connect() from your own button opens just that dialog.

Yes, but you have to wire it up. By default the embedded routes leave your address bar alone, which breaks the back button and makes links unshareable. The SDK gives you a handler that fires on every route change inside the frame, and a navigate method to push a route back into it.

It is a contracted plan billed yearly, sized on how many of your customers automate and how much they run. On our cloud, setup is a subdomain with DNS verification, the origins allowed to frame it, and a signing key. Self-hosted skips the first two, since it already runs on your domain.