PROJECT MANAGEMENT
Weekly RACI gap sweep across active Asana initiatives
Every Monday, scan all active Asana projects for tasks missing a Responsible or Accountable owner and post a per-project gap list to each project lead's Slack DM so they can fill…
How it runs
The automated pipeline, trigger to output.
- TriggerMonday 8am schedule fires
- ActionFetch active Asana projects and incomplete tasksAsana
- LogicFlag tasks missing Responsible assignee or Accountable field
- LogicGroup gaps by project lead
- OutputDM each lead their unowned-task list in SlackSlack
What it does
It runs a weekly audit of your active Asana initiatives, finds every task that lacks a clear Responsible assignee or an Accountable owner (the project lead custom field), and routes a concise gap list to the right lead in Slack. No more silent ownership holes that surface only when a deadline slips.
When to use it
Use it when initiatives span multiple teams and ownership drifts as scope changes. Ideal for PMOs and program managers who run a Monday planning ritual and want unowned work flagged before standup rather than discovered mid-sprint.
How it works
- 1A Monday-morning schedule fires the workflow.
- 2It pulls all Asana projects tagged or filtered as active and expands their incomplete tasks.
- 3A logic step flags tasks with no assignee (Responsible gap) or a blank Accountable custom field.
- 4Gaps are grouped by project and lead.
- 5Each lead receives a Slack DM listing their unowned tasks with direct Asana links and a prompt to assign owners by end of day.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
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.