PERSONAL PRODUCTIVITY
Auto-Unsubscribe From Dead Newsletters in Outlook
Scans your Outlook inbox on a schedule, finds newsletters you never open, calls their List-Unsubscribe link to bulk-unsubscribe, and posts a recap to Slack for approval.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionPull bulk/newsletter mail from Outlook grouped by senderOutlook
- LogicKeep senders with zero opens and a valid unsubscribe link
- ActionCall each List-Unsubscribe endpoint over HTTPHTTP webhook
- ActionRecord processed senders and results in PostgresPostgres
- OutputPost unsubscribe recap to SlackSlack
What it does
Finds subscription email you receive but never read, then quietly unsubscribes from the truly dead ones. It reads the `List-Unsubscribe` header each sender publishes and uses it the way Outlook's own unsubscribe button would, so you stop the flow at the source instead of deleting forever.
When to use it
Run it weekly when your inbox fills with promotional mail you scroll past. Best for operators who want a hands-off cleanup but still want a record of what was touched.
How it works
- 1A weekly schedule fires the workflow.
- 2It pulls the last 90 days of messages flagged as newsletters or bulk mail from Outlook, grouped by sender.
- 3A filter keeps only senders with zero opens and a valid `List-Unsubscribe` mailto or HTTP endpoint.
- 4For each dead sender it calls the unsubscribe endpoint over HTTP.
- 5It writes the sender, message volume, and unsubscribe result to Postgres so the same sender is never re-processed.
- 6It posts a Slack summary listing every sender it unsubscribed from and any that failed.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 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.