PERSONAL PRODUCTIVITY
Triage New Newsletters in Outlook on Arrival
When a new bulk email lands in Outlook, AI classifies whether it is a newsletter you'll likely ignore.
How it runs
The automated pipeline, trigger to output.
- TriggerNew message arrives in OutlookOutlook
- LogicDetect bulk/newsletter headers; pass others through
- ActionClassify keep/archive/digest with OpenAIOpenAI
- LogicBranch on the classification
- ActionArchive out of inbox via OutlookOutlook
- OutputPost one-line digest summary to SlackSlack
What it does
Intercepts promotional and bulk mail the moment it arrives. Instead of waiting for a weekly sweep, it classifies each new newsletter against your historical behavior and either lets it through, auto-archives it, or drops a one-line summary into a digest channel so your inbox stays clear in real time.
When to use it
When you want continuous, low-latency inbox hygiene rather than batch cleanups, and you would rather skim a digest than open each newsletter. Ideal for high-volume inboxes.
How it works
- 1An Outlook trigger fires when a new message arrives.
- 2A filter checks for bulk-mail and `Precedence: bulk` or `List-ID` headers; non-newsletters pass through untouched.
- 3OpenAI classifies the message as keep, archive, or digest using the subject, snippet, and sender history pulled from Postgres.
- 4A branch routes the decision: keep leaves it alone, archive moves it out of the inbox via Outlook.
- 5Digest-classified items get a concise one-line summary posted to a Slack channel.
- 6The classification is logged to Postgres to sharpen future routing for that sender.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Personal Productivity workflows
Email-to-Task: Turn Action-Required Mail Into Linear Issues
Detects mail that contains a concrete task or request, extracts the deliverable and due date, and creates a Linear issue automatically so commitments from email never get lost.
Weekly Low-Attendance Recurring Meeting Auditor
Every Friday, scans the next week of recurring calendar events, flags those where confirmed attendance keeps dropping below a threshold.
Auto-decline focus-block invites unless the organizer is a VIP
Declines meetings that overlap your focus blocks by default, but routes invites from people on your VIP allowlist to a Slack approval prompt so important asks never get…
Auto-create weekly focus blocks around existing meetings and guard them
Every Sunday an agent reads next week's confirmed meetings, carves protected deep-work blocks into the open gaps, sets your Slack status to defend them.
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Weekly Subscription Audit: Find Noisy Lists Worth Unsubscribing
Once a week, analyzes which mailing lists flooded your inbox and how rarely you opened them.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
