Skip to content

Give your automation a chat page.

Publish an automation and it gets a link you can share. People type a question, the automation runs, and the answer comes back in the same thread with text, files and code. You don't build a front end.

Store Desk Published
How did the Berlin store do last week? Flow ran 2 steps
Pulled last week Read the returns log

Berlin, week 14

Revenue landed at €48,210, up 7.4% on the week before. Returns held flat at 3.1%.

Ask for something else

The answer comes back in the thread

Your automation replies with formatted text, code and links, within a 30-second window.

Files go both ways

People can upload a file in the thread, and a reply can send one back, up to 10 MB.

We host the page

Publishing gives the chat its own URL. There is no front end to build and nothing to deploy.

What the chat page handles for you.

A Real Thread

People ask in their own words instead of filling in a form.

One Public Link

Publishing gives the chat a URL. Drafts stay private until then.

Files Both Ways

People upload files, and replies can send files back.

Any Steps In Between

Route by what was asked, call any app, or hand the message to an agent.

Every Message Logged

Each message is a run you can open, read step by step, and retry.

The Limits

A 30-second reply window and 10 MB per file.

Access Control

Only published automations open, and roles still decide who can edit them.

Open Source

The chat trigger and its reply step are part of the MIT-licensed core.

Common questions.

Each message starts a run. Your steps run in order, and a reply step sends the answer back as formatted text plus an optional file. Each visitor keeps a session id that ties their messages together.

Yes. They describe what they want and the assistant builds a real automation, using the accounts and tables already connected in your project. It appears on the canvas for an engineer to review, edit and version.

The reply has to be sent within 30 seconds. Files are capped at 10 MB each on cloud and 25 MB when you self-host. For work that takes longer, answer straight away and send the result another way.

Anyone with the link. The page is public and has no login, so treat the link as the access control. Only published automations open, and project roles decide who can edit the one behind it.

Yes. The chat trigger and its reply step are part of the open-source core, with no account to connect.