PROJECT MANAGEMENT
Block Asana task assignment when assignee is over sprint capacity
Watches for new task assignments in an Asana sprint project, forecasts the assignee's committed hours against their capacity.
How it runs
The automated pipeline, trigger to output.
- TriggerAsana task assigned in sprint projectAsana
- ActionFetch assignee's open sprint tasks and effort estimatesAsana
- LogicSum committed hours vs. capacity threshold
- ActionUnassign task and post overcommit commentAsana
- OutputDM assigner the overage and remaining headroomSlack
What it does
When a task is assigned to someone in an active Asana sprint, this workflow checks whether that person already has enough committed work to fill their sprint capacity. If the new task tips them over, it removes the assignment, adds a clear comment explaining why, and notifies the assigner so the work can be re-routed before it silently slips.
When to use it
Run this on any team that plans sprints in Asana and keeps overloading the same few people. It turns capacity from a number nobody checks into a hard guardrail enforced at the moment of assignment.
How it works
- 1An Asana webhook fires when a task gains an assignee inside the sprint project.
- 2The workflow pulls all of that assignee's open tasks in the sprint and sums their estimated hours from the effort custom field.
- 3It compares the projected total (existing plus the new task) against the assignee's per-sprint capacity.
- 4A branch decides: under capacity, leave it; over capacity, continue.
- 5For overcommit, it clears the assignee field and posts an Asana comment naming the overage.
- 6It sends the assigner a Slack DM with the task link and remaining headroom so they can reassign.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.