PROJECT MANAGEMENT
Roll up Linear release issues into a Trello release card
When a Linear issue is tagged to a release cycle, this updates a single Trello release card with a live checklist of all issues in that cycle and their completion percentage.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue cycle or completion changesLinear
- LogicResolve release cycle and mapped Trello card
- ActionFetch full issue list for the cycleLinear
- ActionRewrite release card checklistTrello
- ActionUpdate card title with percent completeTrello
- OutputNotify Slack when cycle hits 100 percentSlack
What it does
Maintains one Trello card per Linear release cycle. Whenever an issue is added to, completed in, or removed from the cycle, the flow rebuilds the card's checklist so each issue is a checklist item that is ticked when the issue is Done. The card title shows the live percent complete, giving non-engineers a one-glance release readiness view.
When to use it
Use it when leadership tracks releases on a Trello board but the actual scope lives as a Linear cycle. Instead of a manually updated checklist that is always wrong, the release card stays accurate automatically.
How it works
- 1A Linear trigger fires when an issue's cycle assignment or completion state changes.
- 2A logic step identifies the affected release cycle and the mapped Trello release card.
- 3A Linear action fetches the full current issue list for that cycle.
- 4A Trello action rewrites the card's checklist to match, ticking completed issues.
- 5A second Trello action updates the card title with the live completion percentage.
- 6The flow outputs a Slack note when a cycle crosses 100 percent complete.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect TrelloKanban boards for everything.
- 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
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.