PROJECT MANAGEMENT
Alert when mid-sprint Asana adds blow past team capacity
Watches an Asana sprint section and, when a task is added mid-sprint that pushes the committed estimate over the team's capacity, alerts the lead in Microsoft Teams…
How it runs
The automated pipeline, trigger to output.
- TriggerAsana task added to active sprint sectionAsana
- ActionFetch sprint tasks and sum effort estimatesAsana
- LogicStop unless new total overflows team capacity
- LogicRank tasks by priority, pick lowest as cut candidates
- OutputAlert lead in Microsoft Teams with overflow and trade-offsMicrosoft Teams
What it does
Turns scope creep into a capacity decision. It only fires when an added task actually overcommits the sprint, then tells the lead exactly how many hours over they are and surfaces the lowest-priority in-sprint tasks as candidate trade-offs, so the conversation is "what comes out" rather than "did something sneak in."
When to use it
Best for teams that plan in hours against a known capacity and care most about overcommitment, not every individual add. It stays quiet while there's slack and speaks up only when the sprint can no longer hold the work.
How it works
- 1**Trigger** — Asana fires when a task is added to the active sprint section.
- 2**Action** — Fetch all sprint tasks and sum their effort estimates from Asana.
- 3**Logic** — Compare the new total to team capacity; stop unless it now overflows.
- 4**Logic** — Rank in-sprint tasks by priority and pick the lowest as cut candidates.
- 5**Output** — Send the lead a Microsoft Teams alert with overflow hours and suggested trade-offs.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.