How do Slack incoming webhooks receive formatted changelogs?

Slack incoming webhooks accept JSON payloads structured with Block Kit (`header`, `section`, `divider`), rendering rich typography, links, and tags directly inside channel feeds.

Can internal team delivery differ from public customer delivery?

Yes. Delivery configurations support role-based filtering: internal channels receive developer mentions and issue links, while public feeds receive customer-facing summaries.

What happens if Discord rate-limits incoming webhook deliveries?

Delivery workers implement exponential backoff with jitter and respect the `X-RateLimit-Reset` header, ensuring zero dropped release notifications.

Is delivery triggered automatically or requires manual approval?

Delivery occurs only after an authorized team member clicks 'Publish' in Soobrief, preserving strict human-in-the-loop quality control.

Automated Slack and Discord Delivery for Product Changelogs

Deliver approved product changelogs directly into internal Slack and Discord channels via webhooks. Complete architecture and payload design.

Soobrief Team — Product & Engineering, Sooapps · 2026-09-05

In short

Automated Slack and Discord delivery broadcasts approved changelogs directly into team channels via webhook endpoints immediately upon publication. By formatting updates with native Block Kit and Discord embed schemas, teams stay aligned without opening external dashboards.

Writing a great product update is pointless if nobody reads it. Forcing team members to navigate to an external URL or open a bloated PDF ensures that half the company remains in the dark about recent releases.

1. The Delivery Architecture

Delivery operates asynchronously behind a background job queue:


[Human Reviewer Approves Note]
               │
               ▼
   [Database: note_publications]
               │
      [Delivery Dispatcher]
        ├── Slack Webhook Worker ──► #announcements (Block Kit)
        ├── Discord Webhook Worker ─► #dev-updates (Rich Embed)
        └── Email Dispatcher ───────► Newsletter Subscribers

2. Slack Block Kit vs Discord Embed Formatting

Each platform expects specific formatting schemas:

Slack Block Kit: Uses explicit JSON blocks with mrkdwn support, header elements, and actionable buttons linking back to the interactive changelog.
Discord Webhooks: Uses rich embeds with color banners, timestamp footers, and field arrays grouped by category.

3. Guaranteed Delivery and Retry Semantics

Webhook endpoints can fail during platform outages. Soobrief persists every delivery attempt in a publication_deliveries outbox table, retrying failures up to 5 times with exponential backoff before flagging a delivery alert.