PROJECT MANAGEMENT
Daily digest of blockers stuck too long across Asana and Linear
Each morning this scans both Asana and Linear for items in a Blocked state longer than a threshold and posts a ranked aging report to a Slack channel.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday morning schedule
- ActionPull blocked items from AsanaAsana
- ActionPull blocked issues from LinearLinear
- LogicCompute age, filter stale, rank oldest-first
- OutputPost aging digest to Slack channelSlack
What it does
Produces a single daily report of every blocker that has been sitting too long, pulling from both Asana and Linear. It ranks them by how many days they have been stuck and surfaces the owner, so stale dependencies get attention before they slip the schedule.
When to use it
Use it when blockers accumulate quietly and nobody notices a task has been Blocked for two weeks. Great for a program lead or scrum master who wants a standing aging report in the team channel every morning without building a dashboard.
How it works
- 1A scheduled trigger runs each weekday morning.
- 2The flow queries Asana for tasks carrying the Blocked tag and Linear for issues in Blocked states.
- 3A logic step computes days-in-blocked for each item and filters to those past the staleness threshold.
- 4It sorts the combined list oldest-first and formats a digest with owner, age, and source tool.
- 5The digest is posted to a designated Slack channel; if nothing is stale, it posts a short all-clear note.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.