PROJECT MANAGEMENT
Flag a cross-tool dependency from a Slack slash command
An engineer runs a Slack command naming a Linear issue and the Asana task it blocks; the flow links them and marks the Asana task Blocked in one step.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack slash command with both item refsSlack
- LogicValidate and parse Linear + Asana refs
- ActionCross-link the two itemsLinear
- ActionSet Asana task to BlockedAsana
- OutputConfirm dependency in Slack threadSlack
What it does
Lets anyone declare a dependency from where they already are: Slack. A team member fires a slash command with a Linear issue and the Asana task it is blocking, and the flow establishes the link, sets the Asana task to Blocked, and confirms back in the thread.
When to use it
Use it when blockers get discovered mid-conversation in Slack and never make it into the tracker. Ideal for engineering teams who want to capture a dependency the instant they realize it, without tab-switching into two project tools.
How it works
- 1A Slack slash command trigger fires with the Linear issue key and Asana task URL as arguments.
- 2A logic step validates both references resolve to real items and parses the IDs.
- 3The flow stores the link on both sides: the Linear issue ID on the Asana task, and the Asana URL on the Linear issue.
- 4It applies the Blocked tag and status to the Asana task.
- 5It replies in the Slack thread confirming the dependency with links to both items.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect AsanaTasks, projects, milestones — everywhere.
- 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.