PERSONAL PRODUCTIVITY

Daily digest of Outlook promises coming due, posted to Microsoft Teams

Each morning, reviews previously extracted email promises stored in Notion, finds the ones due today or overdue.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily weekday schedule
  • ActionQuery open commitments in NotionNotionNotion
  • LogicFilter to due-today and overdue
  • ActionFormat digest with LLMOpenAI
  • OutputPost digest to Microsoft TeamsMicrosoft Teams

What it does

On a daily schedule, this workflow pulls your tracked email commitments from a Notion database, filters to those due today or already overdue, sorts them by urgency, and posts a single formatted digest to a Microsoft Teams channel. It turns a passive list into a morning briefing.

When to use it

When promises are already being captured but nobody re-opens the tracker. Use it to give yourself or a pod a once-a-day nudge of outstanding follow-ups without polling the database manually.

How it works

  1. 1A morning schedule trigger fires on weekdays.
  2. 2The workflow queries the Notion commitments database for open rows.
  3. 3A logic step filters to commitments due today or overdue and ranks overdue items first.
  4. 4An LLM formats the filtered rows into a concise, human-readable digest with recipient and due date per line.
  5. 5The digest is posted to a designated Microsoft Teams channel as the day's accountability summary.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect Microsoft TeamsChannels, chats, 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.