PERSONAL PRODUCTIVITY

Outlook Approval Emails to Notion Decision Register

Watches an Outlook inbox for approval and sign-off emails, extracts the decision details, and appends a structured row to a Notion decision register database.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Outlook email matching approvals filterOutlook
  • LogicClassify: is this an actual approval decision?
  • ActionExtract decision fields with OpenAIOpenAI
  • OutputAppend structured row to Notion decision registerNotionNotion

What it does

This workflow turns the approvals buried in your email into a clean, searchable decision log. When an Outlook message that grants approval or sign-off arrives, it parses out who decided, what was decided, and when, then writes a structured entry to a Notion database so the record outlives the thread.

When to use it

Use it when approvals happen over email but your team needs a durable register for audits, onboarding, or 'who said yes to this?' moments. Ideal for operations, finance, and program teams that make recurring go/no-go calls in scattered threads.

How it works

  1. 1A new Outlook email arrives matching an approvals filter (subject or label).
  2. 2A classifier checks whether the body actually expresses an approval decision versus a question or FYI; non-decisions are dropped.
  3. 3An OpenAI step extracts structured fields: decision title, approver, outcome, rationale, and effective date.
  4. 4The workflow creates a new page in the Notion decision register with those fields mapped to database properties, linking back to the original message.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect OpenAIModels, embeddings, files.
  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.