PERSONAL PRODUCTIVITY

Extract follow-up promises from sent Outlook mail into a Notion commitment tracker

Scans newly sent Outlook emails for promises you made ('I'll send you...', 'I'll follow up by Friday'), uses an LLM to extract each commitment with its deadline and recipient.

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerevent
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew email sent from OutlookOutlook
  • ActionExtract follow-up promises with LLMOpenAI
  • LogicAny commitments found?
  • OutputCreate commitment rows in NotionNotionNotion

What it does

Every time you send an email from Outlook, this workflow reads the body, asks an LLM whether you made any explicit follow-up promises, and writes each one to a Notion database as a tracked commitment with a recipient, due date, and source-email link. Mail with no promise is skipped silently.

When to use it

For anyone whose sent folder is full of 'I'll get that to you tomorrow' that never gets logged anywhere. Sales reps, account managers, founders, and consultants who promise things in email and want a single accountable list instead of re-reading their own outbox.

How it works

  1. 1A new message lands in your Outlook Sent Items and fires the trigger.
  2. 2The email subject and body are sent to an LLM with a prompt that returns a structured list of commitments (promise text, recipient, inferred due date) or an empty list.
  3. 3A logic step checks whether any commitments were found; if none, the run ends.
  4. 4For each commitment, the workflow creates a Notion database row with the promise, recipient, due date, and a deep link back to the original sent email.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.