PROJECT MANAGEMENT

Daily Sprint Standup Digest from Linear to Slack

Every weekday morning, summarizes the last 24 hours of Linear issue activity into a written standup digest and posts it to your team's Slack channel.

CategoryProject Management
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekday 8:30am schedule
  • ActionFetch Linear issues updated in last 24hLinearLinear
  • LogicFilter out archived and untouched issues
  • ActionSummarize activity into standup digestOpenAI
  • OutputPost digest to Slack channelSlack

What it does

Replaces the live verbal standup with an async written digest. Each morning it pulls every Linear issue that changed in the last 24 hours — status moves, new assignments, completed work, and freshly filed bugs — then uses an LLM to write a tight, readable summary grouped by teammate and posts it to Slack before the workday starts.

When to use it

Use it for distributed or async teams who want standup context without a synchronous meeting, or to give a clean daily record of sprint movement. Best when your team lives in Linear and coordinates in Slack.

How it works

  1. 1A schedule fires each weekday at 8:30am.
  2. 2The flow queries Linear for all issues updated since the previous run, capturing status changes, assignee, and completion state.
  3. 3A filter drops untouched and archived issues so only real activity remains.
  4. 4An LLM step writes the digest: what shipped, what's in progress, and what's newly blocked, grouped per person.
  5. 5The finished digest posts to the chosen Slack channel as a formatted message the team can react to.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LinearIssues, projects, cycles, triage.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.