PERSONAL PRODUCTIVITY
On-Demand Outlook Unsubscribe via Slack Command
Lets a user trigger an unsubscribe from any sender on demand from Slack; the workflow finds that sender's recent mail in Outlook, fires its unsubscribe link.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack command requests an unsubscribeSlack
- ActionFind the sender's latest mail in OutlookOutlook
- LogicExtract and validate the unsubscribe endpoint
- ActionCall the unsubscribe endpoint over HTTPHTTP webhook
- ActionAdd sender to suppression list in PostgresPostgres
- OutputConfirm result in the Slack threadSlack
What it does
Turns unsubscribing into a single Slack message. Instead of digging through Outlook to find the unsubscribe button, you name a sender from Slack and the workflow locates their latest message, extracts the `List-Unsubscribe` endpoint, calls it, and replies with the outcome.
When to use it
When something annoying lands in your inbox and you want it gone now, without waiting for a scheduled sweep. A manual, human-in-the-loop complement to the automated declutter jobs.
How it works
- 1A Slack trigger receives the unsubscribe request with the sender name or domain.
- 2Outlook is searched for that sender's most recent subscription message.
- 3A logic step extracts and validates the `List-Unsubscribe` mailto or HTTP endpoint; if none exists it replies asking to block instead.
- 4The workflow calls the unsubscribe endpoint over HTTP.
- 5The action and result are recorded in Postgres so the sender is on the suppression list.
- 6A confirmation is posted back to the originating Slack thread.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect OutlookMail, calendar, contacts.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 4Connect PostgresAny Postgres URL — query, write, migrate.
- 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.