Turn GitHub releases into Guru knowledge updates for Support and Sales

Build an agent workflow that turns every new GitHub release into a customer-facing knowledge update in Guru, alerts Support and Sales, and posts a TL;DR in Slack.

Trigger: a GitHub webhook on the release event with action "published". Do not use a poll or a cron. The webhook payload gives you the repository, the release id, the tag name, whether it is a draft or prerelease, and the release body.

Filter first. Skip the run entirely if the release is a draft, a prerelease, or the tag name (or release name) contains an internal-only marker like "internal", "internal-only", or "do-not-ship". Only real, customer-facing published releases should continue.

Step 1: Pull the full release from GitHub using Get a Release (by the release id from the webhook payload). Capture the tag name, the release name, the published_at timestamp, the release body (raw Markdown release notes), and the html_url so we can link back to it.

Step 2: Rewrite the raw release notes into a customer-facing summary. Structure it as three short sections: "What shipped" (plain English, one sentence per change, no engineering jargon), "Who is affected" (which customer segments, plans, or personas care), and "What to say to customers" (2 to 4 ready-to-paste talking points Support and Sales can use verbatim). Keep it tight; this is not a changelog, it is enablement copy. Include the tag name and a link back to the GitHub release at the bottom for reference.

Step 3: Find the right Guru card. Use Search Cards in Guru to look for an existing "Product Updates" card (or a feature-specific card if the release touches a single feature area). If a good match exists, use Update Card to append the new release as a new section at the top of the card body, keeping older release sections underneath. If nothing matches, use Create Card to create a new card in the Product Updates collection, assign the right verifier group (Product or the release owner), and set a reasonable verification interval so it stays fresh.

Step 4: Send a Guru Knowledge Alert with Create Announcement, targeting the Support and Sales groups, pointing at the card that was just created or updated. The announcement message should be one sentence: what shipped and why it matters to customers. This is what makes the update actually land in people's Guru inbox instead of quietly sitting in a card.

Step 5: Post a TL;DR in Slack. Use Slack Bot Send a Message to post to #product-updates (make the channel configurable). The message should be two lines: the customer-facing headline, then a link to the Guru card. Keep it scannable.

Idempotency: if the same release id fires the webhook twice, do not double-post. Check the Guru card body for the tag name before appending, and do not send a second announcement or Slack message for a release already published.

Integrations to use: GitHub (Get a Release), Guru (Search Cards, Create Card, Update Card, Create Announcement), Slack Bot (Send a Message).