Automate the work that follows the work
Enable from a library of pre-built flows, combine flows into a workflow that handles a whole job, or describe what you want and watch one get generated. Triggered by your messages, powered by AI.
No code required · Connect any tool via MCP
Ten pre-built flows. 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, customise from there. Everything below ships with the product.
Incoming email → AI drafts a reply in your voice. Only for direct messages from people in your contacts.
Incoming email → AI checks whether a reply is actually needed, drafts only when it is.
Incoming email → AI detects action items → applies a label so they surface immediately.
Email from a specific domain or sender → AI classification → Slack notification.
Scheduled 8am → summarises unread mail from the last 24 hours → sends you a recap.
DoBox task created from a calendar event → AI extracts action items → creates and labels follow-up tasks.
Incoming email + scheduled daily check → identifies threads needing follow-up → tracks them as DoBox tasks.
Scheduled weekly → summarises a Slack channel's activity → emails the digest.
Weekdays 8am → reads unread email + Slack messages → produces a morning summary.
Weekdays 6pm → summarises the last 8 hours of comms → emails you a recap.
Each of these bundles several flows under one objective. Enable the whole thing in one click.
Morning and evening digests plus a quick check-in midday. Three scheduled flows; one coherent rhythm.
Triage incoming, classify priority, draft replies, label and archive. Four flows that turn your inbox into a system that runs without you.
Flows that read from and write to the Brain. Your team's knowledge stays current as a side effect of doing real work.
Scheduled research, summarisation, 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. One trigger (a message arrives, a schedule fires, a task gets created), one set of steps. 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 contains four flows that triage, classify, draft, and archive. The Competitor Intelligence Workflow contains scheduled research, summarisation, and write-back to the Brain. Same primitive at every layer.
Describe what you want. Get a working flow.
Type a prompt. this+that generates the full flow — trigger, steps, 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."
Customize it visually after. Drag nodes, adjust steps, connect new tools. Or just hit run.
Workflows for the work you do every day.
These aren't hypotheticals. Build any of these in minutes.
New email arrives. DoBox task created. Reply drafted. Done.
A new customer emails. Workflows extracts the action item, creates a DoBox task with the context attached, and drafts a reply for your review — all before you've opened the thread.
Meeting ends. Follow-ups assigned. No one takes notes anymore.
Connect Google Meet or Teams. After every meeting, Workflows extracts the action items from the transcript, assigns them to the right people, and sets due dates — automatically.
Invoice hits your inbox. Finance gets notified. You never see it again.
Invoices, receipts, expense reports — Workflows identifies them, forwards to the right person, labels and archives the original. Your inbox stays clear; your finance team stays informed.
Customer asks a question in Slack. The right person is on it in seconds.
Support requests in Slack get classified, routed to the right team member, and tracked as DoBox tasks — without anyone manually forwarding or reassigning.
Workflows read the Brain. Workflows write to it.
Flows that read the Brain ground their answers in what your team actually decided. A sales-pricing flow pulls from your canonical price sheet; a support flow draws on the playbook you've already written down.
Flows that write to the Brain compound knowledge over time. A competitive intelligence flow turns each run into a page; the next run reads the last. Weeks become a searchable history instead of a one-shot report that fades.
See the Brain →Workflows read your calendar. Workflows write to it.
Flows that read the calendar know what is happening before you do. A meeting-prep flow pulls the agenda and attendees an hour before; a follow-up flow extracts action items from a transcript the moment the meeting ends.
Flows that write to the calendar take action without asking. A scheduling workflow finds a 30-minute slot and books it; a workflow that promises a follow-up creates the time on your calendar so the promise becomes a commitment.
See Calendar →If it has an API, it can be a step in your workflow.
Workflows connect to your tools via MCP servers — an open standard for tool integration. CRM, project management, databases, internal APIs — bring in any tool and use it as a workflow step.
This isn't a logo wall. It's an open architecture. If a tool exposes an API, you can connect it. No waiting for an official integration.
Enable a flow. Or build one. Either way, today.
Ten flows and five workflows ship in the product. Build your own from a prompt when you want something different. No code required.
Get startedFree during beta · No code required · Connect any tool via MCP