A Real Thread
People ask in their own words instead of filling in a form.
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.
Berlin, week 14
Revenue landed at €48,210, up 7.4% on the week before. Returns held flat at 3.1%.
Your automation replies with formatted text, code and links, within a 30-second window.
People can upload a file in the thread, and a reply can send one back, up to 10 MB.
Publishing gives the chat its own URL. There is no front end to build and nothing to deploy.
People ask in their own words instead of filling in a form.
Publishing gives the chat a URL. Drafts stay private until then.
People upload files, and replies can send files back.
Route by what was asked, call any app, or hand the message to an agent.
Each message is a run you can open, read step by step, and retry.
A 30-second reply window and 10 MB per file.
Only published automations open, and roles still decide who can edit them.
The chat trigger and its reply step are part of the MIT-licensed core.
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.