PERSONAL PRODUCTIVITY

OKR Rollup Digest from Coda to a Slack Channel

On a weekly schedule it reads the OKR tracker table in Coda, builds a single team-wide rollup with on-track and at-risk counts, and posts the digest to a Slack channel.

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionRead OKR tracker rows from CodaCodaCoda
  • LogicRoll up objectives and classify KR health
  • ActionWrite narrative wins-and-risks summaryOpenAI
  • OutputPost the rollup digest to a Slack channelSlack

What it does

It turns a Coda OKR tracker into a clean weekly digest for the whole team. The workflow reads every row from your OKR table in Coda, groups results by objective, summarizes overall health, and posts one formatted message to a Slack channel so leadership sees status without opening the doc.

When to use it

Use it when Coda is your OKR source of truth and you want a passive, channel-wide status snapshot rather than per-person nudges. Good for all-hands visibility and async leadership reviews.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2It reads all rows from the designated Coda OKR table, including objective, key result, target, current value, and owner.
  3. 3A logic step rolls up each objective and classifies every KR as on-track, behind, or at-risk based on current-versus-target progress.
  4. 4An OpenAI step writes a concise narrative summary with the standout wins and the top risks.
  5. 5It posts the formatted rollup, including counts and the risk list, to the chosen Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CodaDocs, packs, automations.
  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.