PERSONAL PRODUCTIVITY
Auto-assign and follow up on decision owners from Slack
Captures a Slack-thread decision into the register, then opens a tracking task assigned to the named owner and nudges them in Slack if the decision lacks an owner or due date.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack message flagged as decisionSlack
- ActionAgent extracts decision, owner, due dateOpenAI
- LogicOwner and due date present?
- ActionWrite entry to Notion registerNotion
- ActionCreate follow-up task for owner in AsanaAsana
- OutputReply in thread (confirm or request missing info)Slack
What it does
Goes beyond recording a decision to making it accountable. When a decision is flagged in Slack, an agent reads the thread, files it in the Notion register, creates a follow-up task for the owner in Asana, and — if no owner or deadline was stated — posts a polite Slack prompt asking the thread to clarify. Decisions stop falling through the cracks.
When to use it
Use it when your problem isn't capturing decisions but executing them: calls get made and then nobody acts. This adds an ownership and accountability layer so every logged decision has a person and a task attached.
How it works
- 1A Slack emoji reaction or keyword flags a message as a decision.
- 2An agent reads the thread and extracts the decision, rationale, owner, and due date.
- 3A logic branch checks whether an owner and date are present.
- 4If complete, it writes the entry to the Notion register and creates an Asana task assigned to the owner.
- 5If incomplete, it posts a Slack reply asking who owns it and by when.
- 6A confirmation links the register entry and the new task back in the thread.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Connect AsanaTasks, projects, milestones — everywhere.
- 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.