# Weekly Slack nudges for stale Guru cards > Every Monday at 9am, DM each Guru verifier a ranked list of their overdue cards and post a single summary digest in your knowledge-ops Slack channel. - Workflow type: agent - Services: Guru, Slack Bot - Categories: Operations - Published: 2026-06-29 ## What it does - Finds every Guru card that is past its verification interval and groups overdue cards by the verifier who owns them. - Ranks each verifier's queue so the most overdue, highest-traffic answers float to the top, using recent view counts from Guru analytics. - Sends each verifier a friendly Slack DM with their top stale cards, deep links, last-verified dates, and recent view counts. - Posts one weekly summary to your knowledge-ops Slack channel showing total stale cards and a per-verifier count, so leadership can see the backlog at a glance. ## What you'll need - A Guru account with permission to read cards and analytics. - A Slack workspace with the Slack Bot installed and access to your knowledge-ops channel. - Verifiers whose Guru email matches their Slack email so the right person gets the DM. ## Prompt Every Monday at 9am in my workspace's timezone, fan out a prioritized stale-card nudge to each Guru verifier in Slack so their verification queue actually gets worked. Use the Slack Bot integration (not the user Slack integration) so the DMs and channel post come from our shared bot identity. Step 1. Pull the backlog. Call Guru List Unverified Cards to get every card past its verification interval. Page through all results, not just the first page. Step 2. Group by verifier. For each overdue card, use Guru List Card Verifiers to find the user (or group) responsible. Flatten group verifiers into their individual members. Build a map of verifier email to the list of overdue cards they own. Step 3. Rank each verifier's queue. For the date range of the last 14 days, call Guru List Analytics Events filtered to card-view events and count views per card. Then for each verifier, sort their overdue cards by a combined score of (a) how many days overdue the card is and (b) recent view count, so high-traffic stale answers float to the top. Step 4. DM each verifier. For each verifier with at least one overdue card, use Slack Bot Look Up User by Email to resolve their email to a Slack user ID, then Slack Bot Open a Conversation to get a DM channel ID, then Slack Bot Send a Message to post a concise, friendly nudge. The message should list the top 5 cards with the card title as a deep link to the card in Guru, the last-verified date, the number of days overdue, and the recent view count. Skip any verifier with zero overdue cards. If the Slack lookup fails (no matching user, deactivated account, etc.), don't fail the whole run, just record them as unreachable for the summary. Step 5. Post a knowledge-ops summary. After all DMs are sent, post a single digest message via Slack Bot Send a Message to a configurable knowledge-ops channel (let me pick the channel at setup). The digest should show total stale cards across the team, total verifiers nudged, a per-verifier count of overdue cards, and a short list of any orphaned cards whose verifier could not be reached in Slack so an admin can reassign them. Dedupe rule. Track which verifiers were already nudged in the current ISO week and skip anyone who has already been DM'd this week, so re-running the workflow does not double-ping people. Tone for the DM: warm and helpful, not nagging. Something like "Hey, here are your top stale Guru cards this week, ranked by how overdue and how often viewed." Keep it scannable: title, link, last verified, days overdue, recent views. ## How to customize - Change the day or time the nudge runs, or switch from weekly to every other Monday. - Adjust how many cards each verifier sees in their DM (default is the top 5). - Pick a different summary channel, change the ranking rules, or turn the channel digest off entirely. ## FAQ ### Will verifiers with no overdue cards get a Slack message? No. Anyone whose queue is clean for the week is skipped, so the DMs only land for people who actually have work to do. ### How does it decide which stale cards to surface first? It combines how long a card has been overdue with how many times it has been viewed recently, so high-traffic answers that everyone is relying on get fixed before low-traffic ones. ### What happens if a verifier has left the company? Their DM is skipped, but their orphaned cards still appear in the knowledge-ops summary so an admin can reassign them. ### Can I run this more or less often than weekly? Yes. The schedule is a single setting, so you can switch to daily, biweekly, or any cadence that fits your team. ### Will the same person get pinged twice if the workflow runs again in the same week? No. The workflow dedupes so each verifier only gets one nudge per week, even if it runs more than once. Use this prompt in General Input: https://www.generalinput.com/prompts/weekly-slack-nudges-for-stale-guru-cards