PROJECT MANAGEMENT
Flag Issues Added to an Active Linear Sprint
Watches a Linear cycle and posts a Slack alert whenever an issue is created or moved into the cycle after it has already started.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue created or updatedLinear
- LogicKeep only issues added to active cycle after start date
- ActionFetch estimate, assignee, and change actorLinear
- LogicBranch on estimated vs unestimated addition
- OutputPost scope-creep alert to sprint channelSlack
What it does
Monitors the currently active Linear cycle (sprint). When an issue is added to the cycle after its start date, the workflow checks whether it carries an estimate and who added it, then posts a structured alert to your team's Slack channel naming the issue, its points, and the assignee.
When to use it
Run this when your team commits to a fixed sprint scope at planning and you want mid-sprint additions to be visible rather than silent. It catches the "can you just squeeze this in" pattern before it blows the sprint.
How it works
- 1A Linear webhook fires on every issue create or update event.
- 2A filter keeps only issues whose cycle is the active one and whose added-to-cycle timestamp is after the cycle start date.
- 3The workflow fetches the issue's estimate, assignee, and the actor who made the change from the Linear API.
- 4A branch separates estimated additions from unestimated ones, since unestimated work is the bigger risk.
- 5A formatted Slack message lands in the sprint channel with the issue title, points, who added it, and a direct link.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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.