PROJECT MANAGEMENT
Stream Trello Card Completions into a Cycle-Time Warehouse
On every card moved to Done in Trello, calculates its full cycle time and stage breakdown and appends a row to a Postgres table.
How it runs
The automated pipeline, trigger to output.
- TriggerCard moved to Done (Trello webhook)Trello
- ActionFetch card list-movement historyTrello
- LogicCompute total cycle + per-stage durations
- LogicSkip cards with insufficient history
- OutputInsert cycle-time row into PostgresPostgres
What it does
Each time a card lands in a Done list, this workflow reconstructs its journey — total cycle time plus time spent in each stage — and writes a structured record to Postgres. Over weeks it accumulates a clean fact table you can chart, slice by board or label, and use to track flow-efficiency trends without ever touching Trello's API again.
When to use it
Use it when you want durable, analyzable delivery metrics rather than one-off snapshots. Perfect for teams feeding a BI dashboard or wanting to study how cycle time shifts as process changes.
How it works
- 1A Trello webhook fires when a card is moved into a Done list.
- 2The workflow fetches that card's full list-movement history.
- 3A compute step derives total cycle time and per-stage durations from the timestamps.
- 4A guard skips cards lacking enough history to measure reliably.
- 5The final row — card id, board, labels, cycle time, stage splits, completion date — is inserted into the Postgres cycle-time table.
Set it up
What you configure once, before turning it on.
- 1Connect TrelloKanban boards for everything.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.