PROJECT MANAGEMENT
Sync Linear status changes back to the Trello board
When a linked Linear issue changes state, this moves its mirrored Trello card to the matching list so the board reflects real engineering progress without manual dragging.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue changes stateLinear
- LogicResolve linked Trello card or exit
- LogicMap Linear state to target Trello list
- ActionMove card to mapped list and update due dateTrello
- OutputAlert Slack only if the move failedSlack
What it does
Listens for Linear issue state changes and moves the corresponding Trello card into the mapped list (Backlog to Backlog, In Progress to Doing, Done to Shipped). The card always reflects where the work actually stands in the engineering tracker, so non-engineers reading the board never see a stale column.
When to use it
Use it once cards and issues are already linked and you want the Trello board to update itself. It is the reverse direction of card-to-issue intake: here Linear is the system of record for status and Trello is the stakeholder-facing view.
How it works
- 1A Linear trigger fires on an issue state transition.
- 2A logic step looks up the linked Trello card ID stored on the issue; if none exists it exits quietly.
- 3A second logic step maps the new Linear state to the configured Trello list.
- 4A Trello action moves the card to that list and updates its due date if the issue was closed.
- 5The flow outputs nothing further unless the move fails, in which case it posts an alert to Slack.
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
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.