Refresh Guru cards from solved Zendesk tickets

Build an agent workflow that runs every night and turns yesterday's solved Zendesk tickets into Guru knowledge, updating the canonical card when one already exists instead of creating duplicates.

Trigger: a nightly cron, default 2am in the team's time zone. Make the schedule and the lookback window configurable.

Step 1. Use Zendesk Search Tickets to pull every ticket with status:solved updated in the last 24 hours. For each result, call Zendesk List Ticket Comments and grab the most recent public agent comment as the resolution.

Step 2. For each ticket, decide whether the answer is generally reusable. Skip anything that is clearly account-specific (specific customer data, billing adjustments, one-off bug workarounds, anything with PII). Keep concise how-to answers, product behavior explanations, and recurring 'why is this happening' questions. Lean toward skipping when in doubt and surface the count of skipped tickets at the end.

Step 3. For each reusable ticket, call Guru Search With Sources using a short topical query derived from the ticket subject plus the resolution. If the top result looks like a close match on the same topic (not just keyword overlap), treat it as the canonical card.

Step 4a. If a close match exists, call Guru Create Card Comment on that card. The comment should start with 'Suggested update from Zendesk ticket #<id>', quote the new answer cleanly, and @-mention the card's existing verifier so they get notified.

Step 4b. If no close match exists, call Guru Create Card in the designated 'Support drafts' collection. Use a clear draft title phrased as the user's question, rewrite the resolution as a tidy Q&A in the body (question as a heading, answer below), and assign the same verifier the team uses for that topic area. Make the collection slug and default verifier configurable.

Step 5. Once every ticket has been handled, send a single Slack Bot Send a Message to the #support-ops channel summarizing the run: total tickets reviewed, how many were reusable vs skipped, and a bulleted list of every card touched. For each card include its title, whether it was an update or a new draft, the source ticket number, and a deep link to the card in Guru so the SME can review everything in one place. If nothing was actionable, post a short 'no updates today' line so the team knows the job ran.

Guardrails: never duplicate a card the agent already touched in the same run, never re-suggest the same ticket more than once, and keep the Slack message under 25 line items by collapsing the long tail into a 'plus N more' link.