PROJECT MANAGEMENT
Reschedule downstream Asana tasks when a blocking GitHub PR stalls
When a GitHub PR tagged as a release blocker misses its target merge date, the workflow pushes out the dependent Asana tasks by the slip amount and notifies each task assignee.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled blocker-PR deadline check
- ActionRead open release-blocker PRs and milestonesGitHub
- LogicKeep overdue, unmerged PRs and compute slip days
- ActionShift dependent Asana task dates by slipAsana
- OutputComment in Asana and ping assignees in SlackSlack
What it does
When a release-blocking GitHub pull request blows past its target merge date, this workflow shifts the Asana tasks that depend on that merge by the same number of days and tells each assignee their start just moved.
When to use it
Use it when engineering work in GitHub gates downstream delivery tasks tracked in Asana, and a stalled PR otherwise leaves those task dates stale and misleading. It keeps the plan honest automatically.
How it works
- 1A scheduled trigger checks open PRs labeled `release-blocker` against their milestone date.
- 2A filter keeps PRs whose milestone due date has passed without a merge.
- 3The workflow computes the slip in days from the missed target to today.
- 4It looks up the Asana tasks linked to that PR's release section.
- 5For each downstream task it shifts the start and due dates forward by the slip.
- 6It posts an Asana comment on each task and pings the assignee in Slack with the new dates.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 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.