Automate the work that follows the work
Start with the library of pre-built flows, or describe what you want and watch a flow get generated. When one job needs more than that, combine flows into a workflow that handles the whole thing. Flows run when your messages arrive, and AI handles the judgment calls.
No code required · Connect any tool via MCP
Ten pre-built flows and five multi-flow workflows, free to enable
You don't have to build a thing to get value on day one. Enable any of these from the Discover page in your account, customize from there. Everything below ships with the product.
Drafts a reply in your voice when a direct email arrives from someone in your contacts.
AI checks whether an incoming email actually needs an answer, and drafts one only when it does.
Watches incoming mail for action items and labels them so they surface immediately.
A Slack notification whenever email arrives from a sender or domain you care about, with AI doing the classifying.
Every morning at 8, a recap of the unread mail from your last 24 hours.
When a DoBox task is created from a calendar event, AI extracts the action items and turns them into labeled follow-up tasks.
Pairs incoming email with a scheduled daily check to find threads waiting on a follow-up, then tracks each as a DoBox task.
Summarizes a Slack channel's activity each week and emails you the digest.
Weekdays at 8am: unread email and Slack messages, condensed into one morning summary.
The last 8 hours of comms, summarized and emailed at 6pm on weekdays.
Each of these bundles several flows under one objective, and a single click enables the whole thing.
Morning and evening digests plus a quick check-in midday, from three scheduled flows that share one rhythm.
Triage incoming, classify priority, draft replies, label and archive. Four flows that turn your inbox into a system that runs without you.
Bundles the flows that keep the Brain current, so your team's knowledge grows as a side effect of doing real work.
Scheduled research, summarization, and a compounding history page in the Brain. Each run reads the last; weeks become a searchable archive.
PR signals → release notes → team-wide announcement. The day-after-shipping ritual, automated.
Flows are the building blocks; workflows put them together
A flow does one thing. A message arrives, or a schedule fires, or a task gets created, and a set of steps runs. The pre-built library above ships ten of them.
A workflow is a named collection of flows that share an objective. The Inbox Autopilot Workflow, for instance, contains the four flows that keep an inbox moving, while Competitor Intelligence pairs scheduled research with write-back to the Brain. The building blocks stay the same no matter how big the job gets.
Describe what you want and get a working flow
Type a prompt. this+that generates the full flow, from trigger through steps to actions, ready to run. Group several together into a workflow when one job needs more than one trigger.
"Flag every email from a new customer and draft a welcome reply."
Afterward, customize in the visual editor if you want to drag a node somewhere else or wire in another tool. Or just hit run.
Workflows for the work you do every day
Nothing here is hypothetical; any of these comes together in minutes.
The task is created and the reply drafted before you open the email
A new customer emails. Workflows pulls out the action item and creates a DoBox task with the context attached, then drafts a reply and leaves it waiting for your review.
No one takes notes, and the follow-ups still get assigned
Once Google Meet or Teams is connected, the transcript of every meeting gets read for action items, and each one lands with the right owner and a due date already set.
Invoices reach finance without ever cluttering your inbox
Invoices, receipts, expense reports: Workflows spots them on arrival, forwards each to the right person, then labels and archives the original so your inbox stays clear while finance still sees everything.
A support question in Slack reaches the right person in seconds
A support request that lands in Slack gets classified and routed to the right team member as a tracked DoBox task; nobody forwards anything by hand.
Watch a workflow carry one email from arrival to drafted reply
The run classifies the sender, branches on VIP status, then creates a task and drafts a reply, and you never touch any of it.
Not a screen recording. Built from the real FlowEditor node components and animated in code, so it updates with the product instead of going stale.
Grounded in the Brain, and always adding to it
When a flow needs facts, it can pull them from the Brain, so its answers rest on what your team actually decided. The sales-pricing flow quotes your canonical price sheet, and a support flow can lean on the playbook you've already written down.
Writing back is where it compounds: a competitive intelligence flow saves every run as a page in the Brain and starts the next run from it, so after a month you have a searchable history instead of a one-shot report that fades.
See the Brain →Workflows know your calendar and can change it
A flow that reads the calendar knows what is happening before you do: an hour ahead of a meeting, a prep flow pulls the agenda and the attendee list, and the moment the meeting ends, a follow-up flow extracts action items from the transcript.
It runs in the other direction too. A scheduling workflow finds a 30-minute slot and books it, and a workflow that promises a follow-up puts the time on your calendar, which turns the promise into a commitment.
See Calendar →If it has an API, it can be a step in your workflow
Workflows connect to your tools through MCP servers, an open standard for tool integration. Your CRM can be a workflow step. So can your project tracker, a database, or an internal API.
There's no logo wall to check against your stack, because the architecture is open: if a tool exposes an API, you can connect it yourself instead of waiting for an official integration.
Enable a flow today, or build your own from a prompt
Ten flows and five workflows ship in the product, and a prompt gets you a custom one when none of them fit. No code required.
Get startedFree during beta · No code required · Connect any tool via MCP