Smart Slack summaries when Confluence pages change

Whenever a page is created or updated in a watched Confluence space, post a smart summary to the right Slack channel so the team learns about new specs and decisions the moment they land.

Trigger: a Confluence outgoing webhook that fires on the page-created and page-updated events. A Confluence admin will configure the webhook to point at this workflow. The webhook payload includes the page id, the space key, the version number, and the author's account id.

When the webhook fires, do the following:

1) Call Confluence Get Page by ID with the incoming page id and body-format=storage so you have the full page title, storage-format body, current version number, space id/key, and web link.

2) If the incoming event is a page update (version > 1), call Confluence Get Page Versions for the same page and compare the new version against the immediately previous one. Decide whether the edit is material. Skip and stop the run when the change is only whitespace or punctuation, spelling fixes, minor wording tweaks that don't change meaning, formatting-only edits (headings, colors, macros with the same content), or reverts. Continue when the change adds or removes sections, changes a decision, adjusts a spec/scope/date/owner, adds new links or attachments, or otherwise materially alters what the page says. When it's a brand new page (version 1), always continue.

3) Call Confluence Get User by ID with the author's account id from the webhook so you have their display name and profile link to mention in the Slack message.

4) Using the page body, produce: a three-bullet TL;DR (each bullet one sentence, plain English, no jargon dumps); a short 'Key decisions / spec changes' list (0-5 bullets, only include the ones that are clearly stated in the page — never invent); and a single topic tag from this set: product, engineering, ops, security, design, sales, marketing, finance, people, other. Pick the tag that best matches the page's dominant subject.

5) Resolve the destination Slack channel. Use a configurable mapping where each topic tag or space key routes to a channel (for example: product -> #product-updates, engineering -> #eng-changes, security -> #security-notices, default -> #wiki-updates). Fall back to the default channel if the topic tag has no mapping.

6) Call Slack Bot Send a Message to post the summary to that channel. Format it in Slack mrkdwn: a bold header with the page title as a hyperlink to the Confluence web link, one line indicating whether it's new or updated plus the topic tag, the author's name, the three-bullet TL;DR, and the key-decisions list if any. Include a subtle 'skipping minor edits automatically' hint only when useful.

Rules and nuance to bake in:

- Never guess about decisions or spec changes — only surface what the page actually states. If nothing decision-shaped exists, omit that section rather than padding.

- Keep the tone concise and neutral; the goal is that a busy teammate reads the Slack message in ten seconds and knows whether they need to open the page.

- If the webhook fires for a page in a space that isn't in the watched list, exit early without posting.

- Mention the author by display name (not a raw @ ping) unless the user later opts into direct pings.

- If Get Page by ID returns a 404 (page was deleted before the workflow ran), exit silently.