PROJECT MANAGEMENT
Mirror Asana 'Blocked' tasks into Linear as blocking issues
When an Asana task is tagged Blocked, this finds or creates the matching Linear issue, sets it to a Blocked state.
How it runs
The automated pipeline, trigger to output.
- TriggerAsana task tagged 'Blocked'Asana
- LogicConfirm tag added and Linear ID present
- ActionFind or create matching Linear issueLinear
- ActionSet Linear state to Blocked + commentLinear
- OutputWrite Linear link back to Asana taskAsana
What it does
Keeps a one-way mirror of blocked status from Asana into Linear. The moment a planning task picks up a Blocked tag in Asana, the corresponding Linear issue is moved to a Blocked workflow state and cross-linked, so the engineering team working in Linear sees the holdup in their own tool.
When to use it
Use it when product or program managers track delivery in Asana but engineers live in Linear, and blocked work keeps getting silently dropped because the two tools never talk. Ideal for teams that want a single source of truth for *why* something stalled without forcing everyone into the same app.
How it works
- 1An Asana webhook fires when a task gains the 'Blocked' tag.
- 2A filter confirms the change added the tag (not removed it) and that the task carries a Linear issue ID in a custom field.
- 3The flow looks up that issue in Linear; if no link exists, it creates a new issue from the Asana task.
- 4It sets the Linear issue's state to Blocked and posts a comment with the Asana task URL and blocker note.
- 5The Asana task is updated with the Linear issue link to close the loop.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.