PROJECT MANAGEMENT
Prompt the adder to name the stakeholder when a ticket is added mid-sprint
When a Linear issue is added after the sprint is committed, this posts a Slack message to the person who added it asking which stakeholder requested it.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue added to active cycleLinear
- LogicFilter to issues added after cycle commit
- ActionResolve adder's Slack user from Linear emailSlack
- ActionAsk adder to name the requesting stakeholderSlack
- ActionWrite stakeholder back to Linear issue fieldLinear
- OutputPost attribution confirmation in SlackSlack
What it does
Closes the attribution gap at the moment scope grows. The instant someone adds a ticket to a committed sprint, the workflow direct-messages that person in Slack and asks them to name the requesting stakeholder, capturing the answer back onto the Linear issue.
When to use it
Use it when mid-sprint additions are common and you want attribution captured while it's fresh, instead of reconstructing it weeks later. Best for teams that already live in Slack and resist filling out forms.
How it works
- 1A Linear webhook fires on an issue added to the active cycle.
- 2A filter drops issues added before the cycle start so only true scope creep continues.
- 3The flow resolves the adder's Slack identity from their Linear email.
- 4It sends a Slack message with quick-reply buttons listing known stakeholders plus a free-text option.
- 5On reply, the chosen stakeholder is written into a custom field and comment on the Linear issue.
- 6A confirmation is posted back in Slack as the output.
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.