PERSONAL PRODUCTIVITY
Chase OKR Check-In Non-Responders with Escalating Follow-Ups
Mid-week, compares who has submitted their OKR check-in against the full owner roster.
How it runs
The automated pipeline, trigger to output.
- TriggerMid-week pre-deadline schedule fires
- ActionRead full KR owner roster from ClickUpClickUp
- ActionRead submitted check-ins from CodaCoda
- LogicCompute non-responders; split by deadline urgency
- ActionSend firmer second-nudge Slack DMsSlack
- OutputEmail managers for imminent-deadline escalationsGmail
What it does
Closes the gap between who was asked and who actually responded. It cross-references the ClickUp owner roster against the Coda table of submitted check-ins to find non-responders, sends them a firmer second Slack reminder, and — when the deadline is imminent — copies their manager by email so accountability rolls uphill automatically.
When to use it
Use this when the first nudge isn't enough and you're tired of manually figuring out who still owes a check-in. It runs as a scheduled mid-week sweep so the deadline isn't a surprise.
How it works
- 1A mid-week schedule fires before the deadline.
- 2The workflow reads the full list of KR owners from ClickUp.
- 3It reads submitted check-ins from the Coda table and computes the set of owners with no entry.
- 4A logic step splits non-responders by urgency: a standard second nudge, or escalate if the deadline is within 24 hours.
- 5It sends a direct, firmer reminder Slack DM to every non-responder.
- 6For the escalation tier it emails the owner's manager via Gmail noting the outstanding check-in and deadline.
Set it up
What you configure once, before turning it on.
- 1Connect ClickUpDocs + tasks + chats in one workspace.
- 2Connect CodaDocs, packs, automations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect GmailRead, draft, send, label.
- 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 Personal Productivity workflows
Log Outlook promises to Airtable with per-recipient commitment rollups
Captures promises from sent Outlook mail into an Airtable base, linking each commitment to a recipient record so you get a running per-contact view of everything you've promised…
Turn Outlook email promises into assigned Asana tasks with due dates
When you send an email containing a commitment, an LLM extracts the promise and its deadline and creates a corresponding Asana task assigned to you with the due date set.
Auto-decline low-priority invites that collide with deep-work blocks
When a new calendar invite lands on top of a protected deep-work block, an AI scores its priority and auto-declines low-value meetings with a polite note proposing alternative…
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Monthly Meeting Cost Report by Email
On the first of each month, tallies every recurring meeting's total person-hours across the team, converts to an estimated dollar cost.
Auto-create weekly focus blocks around existing meetings and guard them
Every Sunday an agent reads next week's confirmed meetings, carves protected deep-work blocks into the open gaps, sets your Slack status to defend them.
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.