PROJECT MANAGEMENT
Real-time blocker logging to a Coda dependency tracker
When a Linear issue is moved into a Blocked state, it instantly logs the dependency, the teams involved.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue status-change webhookLinear
- LogicKeep only transitions into Blocked
- ActionUpsert blocker row into Coda trackerCoda
- OutputNotify blocking team in SlackSlack
What it does
The moment a Linear issue transitions into a Blocked status, this workflow captures it as a row in a Coda dependency-tracker table — recording the blocked team, the team being waited on, the timestamp, and the stated reason. It then notifies the team that owns the unblock so the handoff is visible from the first minute.
When to use it
Use it when program leads want a living source of truth for cross-team dependencies rather than a once-a-day snapshot. Coda becomes the audit log of every blocker as it forms and clears.
How it works
- 1A Linear webhook fires on issue status changes.
- 2A filter keeps only transitions into a Blocked state on dependency-labeled issues.
- 3The workflow extracts the waiting team, blocking team, and reason from the issue fields.
- 4It upserts a row into the Coda tracker table, marking the blocker as open.
- 5It posts a Slack alert to the blocking team's channel with a link back to both the Linear issue and the Coda row.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect CodaDocs, packs, automations.
- 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.