PERSONAL PRODUCTIVITY

At-Risk OKR Manager Alert from ClickUp to Teams

Weekly it scans ClickUp goal and task progress, isolates only the key results that are behind pace or stalled, and sends each manager a focused at-risk briefing in Microsoft Teams.

CategoryPersonal Productivity
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionRead ClickUp goals and linked task progressClickUpClickUp
  • LogicCompute pace and keep only at-risk KRs
  • ActionDraft reason and next step per at-risk KROpenAI
  • LogicSkip managers with no at-risk KRs
  • OutputSend focused at-risk briefing in TeamsMicrosoft Teams

What it does

It gives managers a signal, not noise. Rather than reporting on every objective, the workflow inspects ClickUp goals and their linked tasks, flags only key results that are behind expected pace or have had no completed tasks recently, and delivers each manager a Teams message listing just their at-risk KRs with the underlying reason.

When to use it

Use it when ClickUp holds your goals and tasks and managers are drowning in green-status updates. It surfaces the few OKRs that actually need a conversation before the weekly review.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2It reads ClickUp goals and their linked task completion and due-date data.
  3. 3A logic step computes expected-versus-actual pace per KR and keeps only those behind pace or with zero recent completions.
  4. 4An OpenAI step writes a one-line reason and a suggested next step for each at-risk KR.
  5. 5A logic gate skips managers with no at-risk KRs this week.
  6. 6It sends each remaining manager their focused at-risk briefing in Microsoft Teams.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ClickUpDocs + tasks + chats in one workspace.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  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.