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 a message arrives, when a schedule fires, or when you press go, and AI handles the judgment calls.
No code required · Connect any tool via MCP
Enable a flow, a workflow or an agent on your first day
Everything below ships with the product, on the Discover page in your account. The catalog is organized by work area, so leadership, sales, marketing, engineering, operations, support, finance, HR and legal each have their own set. Turn one on, then customize it.
Reads each new email and works out whether it genuinely needs a reply. If it does, it learns your tone from your recent sent mail and leaves a draft in your inbox.
Runs on Primary-category mail only. It skips notifications and threads that are already settled, and drafts in your style, in the language the message arrived in.
Watches incoming mail for anything that needs you to do something, and labels it Action Required.
Name the senders and domains you care about. Mail from any of them reaches you in Slack with the subject, a preview and a link to open it.
Every morning at 8, the unread mail from your last 24 hours, grouped by urgency and sent to your inbox.
When your meeting-notes assistant emails the summary, every action item in it becomes a DoBox task with a link back to the source and a due date if one was named.
Each weekday morning it checks the mail you sent in the past week. Anything still unanswered becomes a DoBox reminder to chase it.
Summarizes the Slack channels you care about once a day, calls out whatever needs your attention, and sends it to you as a direct message.
Weekdays at 8am: the Slack channels you follow and your primary inbox since last night, grouped by urgency, with the top few things pulled to the front.
At 6pm on weekdays, the mail you sent and received and the meetings you sat in, grouped by what still needs something from you.
A workflow groups several flows under one objective, and setup turns all of them on together. A few of the ones that ship, across different teams:
Classifies and labels every email on arrival, drafts a reply where one is needed, drafts your meeting follow-ups, and delivers a morning digest.
Builds a knowledge base from your public Slack channels and email, so decisions and context land in the Brain on their own. Anything sourced privately waits for your approval in DoBox.
Seeds a page per competitor, watches their features and pricing, and posts a weekly briefing to Slack. Each run reads the last, so the Brain pages compound into a history.
An AI review lands on every pull request the moment it opens, and the reviewers get pinged. A PR going stale gets a nudge before anyone forgets it.
Labels, queues and drafts a first reply for every message arriving in the shared support inbox, so whoever opens it finds a worked queue.
Runs the close checklist end to end: chases owners for accruals and variance explanations, and posts a daily status to Slack.
Triages incoming applications, chases interview feedback, and assembles the debrief packet before the committee sits down.
Builds a register of every vendor contract from your inbox and warns you before each cancellation window closes.
An agent gets a written brief and a set of tools rather than a fixed sequence of steps, so it works out its own route to the outcome. Run one from chat, or call it from a flow step when the next move depends on what the message actually says. The setup wizard shows you an agent's brief and its tools before you install it.
Summarizes yesterday's Slack conversations into the decisions that were made and the questions still open.
Researches a company or a person across the web and your contacts, and comes back with a structured briefing.
Answers the sales team's competitor questions from your battlecards, then updates the page with whatever it had to look up.
Every message in a shared support inbox gets classified and labeled. The straightforward ones come back drafted; the rest become tasks for a person.
Turns raw notes and threads into organized Brain pages, and keeps the space tidy as more arrive.
Finds supplier invoices sitting in your inbox, turns each one into a tracked task, and chases the approver until the payment run is ready.
Reads incoming applications and writes an evidence-based screening note against the role's written requirements.
Reads executed contracts as they land and records the dates that matter. You hear about a notice window while you can still act on it.
An agent is yours until you share it. Share one with your team and it shows up in their account under Team agents; add it to your board agents and it becomes one of the delegate options on DoBox task cards.
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 fixed set of steps runs. The path is the same every time.
A workflow is a named collection of flows that share an objective. Inbox Autopilot groups the flows that classify mail, draft replies, handle meeting follow-ups and send you a morning digest, while Competitor Intelligence pairs scheduled research with write-back to the Brain.
An agent is the third piece, and it works the other way around. You hand it a brief and a set of tools, and it picks its own moves each time it runs. A flow step can pass a job to an agent when the right next action depends on what actually arrived.
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.
One workflow turns a customer email into a tracked task and a drafted reply
A new customer emails. Set up this flow once and it pulls out the action item, creates a DoBox task with the context attached, then drafts a reply and leaves it in your queue for review. You point it at the messages you want it to handle.
No one takes notes, and the follow-ups still get assigned
Your notetaker already emails you the summary. When that arrives, whether it comes from Granola, Fathom, Otter or Gemini, every action item in it becomes a task 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 for you to review before it sends.
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: on a morning schedule, a prep flow pulls the agenda and the attendee list for the day's calls. Afterwards, when your notes assistant emails the summary, a follow-up flow turns the action items into tasks.
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 runs an MCP server, 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 service you put behind one.
There's no logo wall to check against your stack, because the architecture is open: if a tool runs a hosted MCP server, you point us at its URL and connect it yourself instead of waiting for an official integration. It runs the other way too. Our own MCP server lets Claude or ChatGPT work inside this+that, reading and creating tasks, searching and writing brain pages, and handling groups, labels, rules and recurring work.
Enable a flow today, or build your own from a prompt
Flows, workflows and agents all ship in the product, and a prompt gets you a custom flow when none of them fit. No code required.
Get startedFree for 30 days · No credit card required · No code required · Connect any tool via MCP