PROJECT MANAGEMENT
Block over-capacity Asana assignments in real time
When a task gets assigned in Asana, it checks whether the assignee's total sprint hours now exceed capacity and immediately DMs the assigner on Slack to confirm or reassign.
How it runs
The automated pipeline, trigger to output.
- TriggerAsana event: task assigned / reassignedAsana
- ActionFetch assignee's open tasks + hours across boardsAsana
- LogicSum hours vs. remaining capacity
- LogicBranch: over capacity vs. within
- OutputDM the assigner on Slack to confirm or reassignSlack
What it does
The moment someone is assigned a task, this workflow recomputes that person's total estimated hours for the sprint across all boards. If the new task pushes them past capacity, it sends a real-time warning to whoever made the assignment so they can rebalance before work starts.
When to use it
Use it on fast-moving teams where work is assigned ad hoc throughout the sprint, not just during planning. It moves the overcommit check from a weekly report to the exact moment a decision is made.
How it works
- 1An Asana event fires when a task's assignee changes or a new task is assigned.
- 2Pull that assignee's open tasks and estimated hours across every active project.
- 3Sum the hours and compare to the assignee's remaining sprint capacity.
- 4Branch: if still within capacity, exit quietly; if over, continue.
- 5Build a concise warning with the task name, the assignee's new total, and the overage.
- 6DM the assigner (and optionally the assignee) on Slack with a reassign prompt.
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
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.