PROJECT MANAGEMENT
Flag Trello cards blocked by open GitHub dependencies
On a daily schedule, checks each Trello card's referenced GitHub pull requests and labels the card Blocked when a required PR is still open or has failing checks.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionPull cards and extract referenced PR linksTrello
- ActionFetch PR state and check statusGitHub
- LogicDecide which cards have unmet dependencies
- ActionApply or clear Blocked label with reasonTrello
- OutputPost newly-blocked digest to SlackSlack
What it does
Reads every card in your active Trello lists, finds the GitHub PR links referenced in each card, and inspects those PRs. If a card depends on a PR that is still open, has merge conflicts, or has failing checks, the card gets a red "Blocked" label and a comment naming the offending PR. Cards whose dependencies have all merged get the label removed.
When to use it
Use it when cards regularly wait on engineering pull requests and your board silently lies about what is actually unblocked. It keeps the Blocked state honest without anyone manually checking GitHub.
How it works
- 1A scheduled trigger runs each morning.
- 2A Trello action pulls all cards from the configured lists and extracts GitHub PR URLs.
- 3A GitHub action fetches the state and check status for each referenced PR.
- 4A logic step decides per card whether any dependency is unmet.
- 5A Trello action applies or clears the Blocked label and comments the reason.
- 6The flow outputs a Slack digest of newly blocked cards.
Set it up
What you configure once, before turning it on.
- 1Connect TrelloKanban boards for everything.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.