PERSONAL PRODUCTIVITY

Propose Outlook Inbox Rules for Recurring No-Action Senders

Analyzes which senders you consistently ignore, uses AI to draft folder/archive rules for each.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonthly schedule starts the run
  • ActionRead inbox engagement history from OutlookOutlook
  • LogicIsolate recurring senders with no engagement
  • ActionDraft a rule + rationale per sender with OpenAIOpenAI
  • ActionStore proposals for audit in PostgresPostgreSQLPostgres
  • OutputSend approve/skip proposals to SlackSlack

What it does

Looks at senders whose mail you never reply to, open, or flag, then proposes a tidy Outlook rule for each one (auto-archive, move to a folder, or mark read). Nothing is applied automatically. You approve the rules you want.

When to use it

When recurring senders like status digests, ticketing notifications, or vendor updates clutter your inbox but you do not want to unsubscribe outright. Run it monthly to keep rules current as your traffic shifts.

How it works

  1. 1A monthly schedule starts the run.
  2. 2It reads the last 60 days of inbox activity from Outlook, including which messages were opened, replied to, or deleted unread.
  3. 3A filter isolates senders with three or more messages and no engagement.
  4. 4OpenAI reviews each ignored sender and the message subjects to suggest a specific rule and target folder, with a short rationale.
  5. 5The proposals are stored in Postgres for an audit trail.
  6. 6Each proposal is sent to Slack with approve and skip buttons so you decide what becomes a real Outlook rule.

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 PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  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.