PROJECT MANAGEMENT
Clear Asana blockers when the upstream Linear issue is resolved
When a linked Linear issue moves to Done, this removes the Blocked tag from the dependent Asana task and notifies the owner that work can resume.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue moved to DoneLinear
- LogicCheck issue is a linked Asana blocker
- ActionRemove Blocked tag, set Asana task ReadyAsana
- ActionComment resolution on Asana taskAsana
- OutputDM the assignee that work is unblockedSlack
What it does
Closes the reverse half of the blocker loop. When the Linear issue that was holding up an Asana task is completed, the flow automatically lifts the Blocked tag on the Asana side and pings the task owner that they are clear to proceed.
When to use it
Use it alongside any Asana-to-Linear blocker mirror so that resolved dependencies don't leave Asana tasks stuck as Blocked forever. Perfect for teams tired of manually chasing 'is this unblocked yet?' updates after engineering ships the fix.
How it works
- 1A Linear webhook fires when an issue transitions to a Done or Completed state.
- 2A filter checks that the issue is linked to an Asana task (via the stored Asana GID) and was previously a blocker.
- 3The flow removes the 'Blocked' tag from the dependent Asana task and updates its status to Ready.
- 4It posts a comment on the Asana task noting which Linear issue cleared the blocker.
- 5A direct Slack message goes to the Asana task assignee letting them know they can resume.
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
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.
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.
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.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
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.