Turn emails, Slack messages, and meeting notes into action items

Scans your inbox, Slack, and meeting notes for things you owe people, and drafts the reply for each one.

How the work actually flows

It branches. Every path runs; all paths must finish before it continues; runs once per each action item.

Pattern: Parallel Split (2) · Synchronisation (3) · Multiple Instances without Synchronization (12)

flowchart TD trig(["scheduled scan of channels"]):::trigtime s0["identify who is waiting"]:::task s1[["draft reply for each item"]]:::mi s2[("save list ordered by urgency")]:::store trig --> s0 s1 --> s2 gx{"+ which channel to scan"}:::gate s0 --> gx p00["scan email"]:::task gx -->|"email"| p00 p10["scan slack messages"]:::task gx -->|"slack"| p10 p20["scan meeting notes"]:::task gx -->|"meeting notes"| p20 jn{"+ combine commitments"}:::gate p00 --> jn p10 --> jn p20 --> jn jn --> s1 out[/"tracked list of commitments with drafts"/]:::out pay{{"replies sent on time every time"}}:::pay s2 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepRuns once per itemA record or sheetEvery pathWaits for allResultPayoff
Build size
Starter

A small build with a couple of connected tools.

Business functions
General Automation
Connects
GmailSlackNotionFireflies

The problem it solves

Promises and follow-ups get scattered across email, Slack, and meeting notes, and it's easy to forget who you told you'd get back to. You end up apologizing for slow replies instead of just sending them on time.

Who it fits

Anyone juggling commitments across email, chat, and meetings who needs a single list of what's owed and to whom.

How it works

  1. Scans your email, Slack messages, and meeting notes for commitments and requests
  2. Identifies who is waiting on a response and how urgent it is
  3. Drafts a reply for each action item based on the context
  4. Saves every item and draft to a tracked list, ordered by urgency
What you get

Commitments tracked with a reply drafted for each

Every commitment you owe someone across email, Slack, and meetings lands in one list, with a reply already drafted for you.

What you get

A running list of open commitments with a ready-to-send draft reply for each one.

What you need

Gmail, Slack, and Notion accounts, plus a meeting notes tool if you use one.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook