PROJECT MANAGEMENT
Auto-reassign aging Trello cards to an available owner
When a Trello card crosses its idle threshold, this workflow checks the current owner's calendar for availability and reassigns the card to the next free teammate.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule starts board sweep
- ActionFetch idle cards past thresholdTrello
- ActionRead assignee calendar availabilityGoogle Calendar
- LogicPick next available owner if assignee is busy
- ActionReassign card to new ownerTrello
- OutputAnnounce handoff in SlackSlack
What it does
This workflow watches for Trello cards that have gone idle past a set number of days and decides whether the current owner can still act on them. It checks that owner's Google Calendar for out-of-office or heavy booking, and if they are unavailable it reassigns the card to the next teammate whose calendar is clear, then announces the handoff in Slack.
When to use it
Use it when cards stall because the assignee is on leave, in back-to-back meetings, or overloaded. It keeps work moving without a manager manually rebalancing the board.
How it works
- 1A daily schedule starts the sweep across the target board.
- 2The workflow fetches cards whose last activity exceeds the idle threshold from Trello.
- 3For each card it reads the assignee's Google Calendar to gauge availability over the next few days.
- 4A logic step decides: if the owner is free, leave the card; if not, pick the next available teammate from the pool.
- 5The card is reassigned to the chosen owner in Trello.
- 6A handoff message is posted to Slack tagging the old and new owners.
Set it up
What you configure once, before turning it on.
- 1Connect TrelloKanban boards for everything.
- 2Connect Google CalendarEvents, attendees, availability.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.