PROJECT MANAGEMENT
Mirror new Trello cards into Linear issues
When a card lands in a designated Trello list, this creates a matching Linear issue and writes the issue URL back onto the card so both tools share one source of truth.
How it runs
The automated pipeline, trigger to output.
- TriggerNew card added to watched Trello listTrello
- LogicSkip if card already linked to a Linear issue
- ActionCreate Linear issue from card fieldsLinear
- ActionWrite Linear link back onto Trello cardTrello
- OutputPost created-issue confirmation to SlackSlack
What it does
Watches a specific Trello list (for example a "Ready for Engineering" column) and, for every new card, opens a corresponding Linear issue with the card's title and description carried over. It then comments the new issue link back on the Trello card so stakeholders and engineers are always looking at the same work item.
When to use it
Use it when product or operations triage in Trello but engineering executes in Linear. It removes the manual copy-paste handoff and the inevitable drift where a card exists but no issue was ever filed.
How it works
- 1A Trello trigger fires when a card is added to the watched list.
- 2A logic step checks the card has no existing Linear link in its description, preventing duplicates on re-triggers.
- 3A Linear action creates an issue in the mapped team, mapping the card title, body, and any matching label.
- 4A Trello action attaches the Linear issue URL and ID to the card as a comment and custom field.
- 5The flow outputs a Slack confirmation to the intake channel with both links.
Set it up
What you configure once, before turning it on.
- 1Connect TrelloKanban boards for everything.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.