PROJECT MANAGEMENT
Reconcile mismatched blocker states between Asana and Linear
A scheduled agent audits linked Asana and Linear items, finds pairs where one says Blocked and the other doesn't, decides the correct state, and fixes the drift.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly reconciliation schedule
- ActionPull linked pairs from Asana + LinearAsana
- LogicDetect state mismatch and judge correct state
- ActionUpdate the out-of-date sideLinear
- OutputPost reconciliation summary to SlackSlack
What it does
Runs a reconciliation pass over every linked Asana-Linear pair and repairs blocker drift. When one tool shows an item as Blocked but its counterpart looks open and active, the agent reasons about which state is current and brings both into agreement, logging every correction it makes.
When to use it
Use it as a safety net behind your real-time sync flows, which can miss events during outages or manual edits. Best for teams running active two-way blocker mirroring who want a nightly self-healing audit instead of discovering inconsistencies during a release.
How it works
- 1A nightly schedule triggers the reconciliation agent.
- 2The agent pulls all cross-linked pairs from Asana and Linear and compares their blocker states.
- 3For each mismatch it inspects recent activity and comments to decide which side reflects reality.
- 4It updates the out-of-date side, removing or applying the Blocked status to match.
- 5It compiles every change into a reconciliation summary and posts it to Slack for the team to review.
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.