PROJECT MANAGEMENT
Cross-board capacity rollup from Postgres to MS Teams
Queries a Postgres warehouse that mirrors multiple PM boards, computes per-assignee load versus sprint hours, and posts a department-wide overcommit digest to Microsoft Teams.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: daily capacity digest
- ActionRun per-assignee hours rollup queryPostgres
- LogicCompute utilization vs. sprint capacity
- LogicFlag assignees over threshold
- OutputPost overcommit digest to MS TeamsMicrosoft Teams
What it does
For orgs that sync several project tools into a Postgres warehouse, this runs one SQL rollup to total each person's committed hours across all boards, compares it to their sprint capacity, and delivers a department overcommit digest to a Microsoft Teams channel.
When to use it
Use it when capacity data already lands in a data warehouse and you want a single source-of-truth report that spans tools (Asana, Jira, Linear, etc.) rather than querying each board's API separately.
How it works
- 1A schedule triggers the digest (e.g. daily at 6am).
- 2Run a parameterized Postgres query that sums estimated hours per assignee for the active sprint window.
- 3Join against the capacity table and compute utilization percentage per person.
- 4Branch: flag everyone above the overcommit threshold (e.g. >100%).
- 5Render a ranked digest grouped by team, with utilization bars and overage hours.
- 6Post the digest to the relevant Microsoft Teams channel for managers.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 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.