Ship it as a form, a chat, an API, or a Slack bot.
A published workflow is reachable the way the people who use it already work. Share a link, embed it, wire it into Slack or Teams, or call it from your own system.
Built in. Nothing to configure.
A page anyone can fill in
Each input becomes a field. Send the link to the person who used to send you the email.
A conversation, with memory
A hosted chat where every turn is a governed run. The model remembers the thread for as long as you tell it to.
An endpoint for your own code
Run, form, and chat endpoints per workflow, called with a deploy key you can rotate.
Links with the right lock
Public, password, email-domain, or sign-in required. A password grant lasts twelve hours.
Inside your own site
A signed embed token puts the form or chat on a page you control, and nowhere else.
Slack and Microsoft Teams
Bind a workflow to a channel and run it from a message. Replies come back where the question was asked.
Three steps, then it runs.
- Publish the workflowThe readiness gate checks credentials and wiring first.
- Pick the interfaceForm, chat, batch, or API, one per published version.
- Choose who can reach itShare link settings, an embed token, a Slack channel binding, or an API key.
Meets your team where it already works.
One workspace, the rest of the job.
See it on your stack.
30 minutes with our team. We'll walk you through governance, audit, evals — and answer everything procurement will ask. Bring your own NDA; we'll sign in 24 hours.