PERSONAL PRODUCTIVITY

Outlook Decision Capture to Coda with Teams Confirmation

When a decision email lands in Outlook, it logs a structured entry to a Coda decision table and replies in Microsoft Teams asking the decision owner to confirm the captured record.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Outlook decision emailOutlook
  • ActionExtract decision, owner, and date with OpenAIOpenAI
  • ActionInsert 'pending' row in Coda decision tableCodaCoda
  • OutputPost confirmation prompt to decision owner in TeamsMicrosoft Teams

What it does

This workflow captures email decisions and closes the loop with the owner. On an inbound Outlook decision email, it extracts the decision and owner, writes a row to a Coda decision table, and posts a confirmation prompt in Microsoft Teams so the owner can verify the record is accurate before it becomes the source of truth.

When to use it

Use it when decision accuracy matters more than speed and you want a human checkpoint. Suited to teams already living in Coda and Teams that want decisions confirmed, not just logged.

How it works

  1. 1A new Outlook email arrives matching a decision filter.
  2. 2An OpenAI step extracts the decision statement, owner, and effective date.
  3. 3The workflow inserts a row into the Coda decision table marked 'pending confirmation'.
  4. 4It posts a message to the owner in a Microsoft Teams channel summarizing the captured entry with a link to the Coda row.
  5. 5The owner confirms or corrects directly in Coda, flipping the row's status.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect CodaDocs, packs, automations.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  4. 4
    Connect OpenAIModels, embeddings, files.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.