PROJECT MANAGEMENT
Mirror a Linear blocker onto its dependent Asana tasks
When an engineering issue is blocked in Linear, flags the linked downstream Asana tasks owned by other teams and notifies their leads in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue marked blocked (webhook)Linear
- ActionRead linked downstream Asana task referencesLinear
- LogicSkip issues with no Asana links
- ActionTag and comment at-risk Asana tasksAsana
- OutputNotify Asana project leads in SlackSlack
What it does
When a Linear issue is marked blocked, this workflow finds the Asana tasks that depend on it through a shared reference field, adds an at-risk flag and comment to each, and pings the responsible Asana project leads in Slack. It keeps a blocker logged in engineering's tool visible to the operations and GTM teams who track work in Asana.
When to use it
Use it when engineering lives in Linear but other teams plan in Asana, and a Linear blocker invisibly stalls an Asana milestone. This bridges the two tools automatically.
How it works
- 1A Linear webhook triggers when an issue enters a Blocked state.
- 2The flow reads a cross-reference field linking the issue to downstream Asana task IDs.
- 3A filter skips issues that carry no Asana links.
- 4Each linked Asana task gets an at-risk tag and a comment citing the upstream Linear blocker.
- 5The Asana project lead is notified in Slack with the blocker context and a link back to the Linear issue.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect AsanaTasks, projects, milestones — everywhere.
- 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.