PROJECT MANAGEMENT
Weekly Sprint Health Report from Linear to Notion + Slack
Every Friday, pulls the active Linear sprint's issue data, has an LLM write a plain-English health summary, publishes it as a Notion page.
How it runs
The automated pipeline, trigger to output.
- TriggerFriday weekly schedule fires
- ActionFetch active cycle issues from LinearLinear
- LogicCompute completion, carryover, scope-added metrics
- ActionDraft narrative health summary with LLMOpenAI
- ActionPublish dated report page in NotionNotion
- OutputPost report link to stakeholder Slack channelSlack
What it does
Generates a polished weekly sprint health report from your Linear data and delivers it to non-engineering stakeholders without anyone writing it by hand. The report covers scope completed, work still open, scope added mid-sprint, and any blocked issues, in language a non-technical reader can follow.
When to use it
When your team runs sprints in Linear and leadership keeps asking "how's the sprint going?" Run it on a recurring Friday schedule so the answer is waiting before anyone asks. Best for teams that want a durable written record in Notion plus a quick Slack ping.
How it works
- 1A weekly schedule fires every Friday afternoon.
- 2Pull the active cycle's issues from Linear, including status, estimate, assignee, and labels.
- 3Compute completion percentage, carryover count, and scope-added count from the issue set.
- 4An LLM turns the metrics into a clear narrative summary with a health rating.
- 5Create a dated Notion page in the sprint-reports database with the full writeup.
- 6Post the Notion link and one-line headline to the stakeholder Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.
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…
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.
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.
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.