PROJECT MANAGEMENT
On-demand capacity snapshot to Airtable and Slack
A webhook triggers a point-in-time capacity scan across Asana boards, writes each assignee's load and overage to an Airtable log, and Slacks a summary of who is overcommitted.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: on-demand snapshot requestHTTP webhook
- ActionFetch per-assignee hours across Asana boardsAsana
- LogicCompute committed, capacity, and overage
- ActionAppend timestamped rows to Airtable logAirtable
- OutputSlack summary of overcommitted assigneesSlack
What it does
Fire this workflow whenever you want a fresh capacity reading. It scans Asana load per assignee against sprint hours, appends a timestamped snapshot row per person to an Airtable table so you can track utilization trends over time, and posts a Slack summary of anyone currently over capacity.
When to use it
Use it for mid-sprint check-ins, retro prep, or whenever scope changes and you need an immediate before/after capacity record rather than waiting for the next scheduled report.
How it works
- 1An inbound webhook (button, form, or CI hook) triggers the snapshot.
- 2Pull open tasks and estimated hours per assignee across active Asana projects.
- 3Compute committed hours, capacity, and overage for each person.
- 4Append one timestamped row per assignee to the Airtable utilization log.
- 5Branch: select only the overcommitted assignees for the alert.
- 6Post a concise overcommit summary to Slack with a link to the Airtable log.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect AirtableBases, tables, views, automations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.
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…
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.
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.
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.