PERSONAL PRODUCTIVITY

Weekly OKR Check-In Opener with Owner Nudges

Every Monday, opens the weekly OKR check-in by reading active key results from ClickUp and sending each owner a personal Slack DM asking for their progress and confidence rating.

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule fires
  • ActionRead active key results + owners from ClickUpClickUpClickUp
  • LogicGroup KRs by owner; skip owners with none
  • ActionSend each owner a personalized check-in DMSlack
  • OutputPost 'check-in window open' note to team channelSlack

What it does

Kicks off the weekly OKR ritual automatically. It pulls every active key result and its owner from ClickUp, then sends each owner a direct, personalized Slack message listing only the KRs they own and asking for a status update plus a confidence rating (on track / at risk / off track).

When to use it

Use this when check-ins are slipping because someone has to manually remember who owns what and chase them every week. Run it as the standing kickoff for any team that tracks OKRs in ClickUp and lives in Slack.

How it works

  1. 1A weekly schedule fires Monday morning.
  2. 2The workflow queries ClickUp for key results in the current cycle that are still open.
  3. 3It groups those KRs by their assigned owner so nobody gets a generic blast.
  4. 4A branch skips owners with zero active KRs to avoid noise.
  5. 5For each remaining owner it composes a Slack DM listing their specific KRs with a prompt for progress and a confidence label.
  6. 6The DMs are delivered and a single summary line is posted to the team channel confirming the check-in window is open.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ClickUpDocs + tasks + chats in one workspace.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.