Inspect an unsent notification payload before connecting Slack or Teams

Description and use

Inspecting an unsent notification payload enables early detection of content and truncation issues before sending to Slack, Teams, or generic webhooks, reducing downstream errors.

Problem

Review notification content and truncation before sending to Slack, Teams, or generic webhooks to avoid missing attribution, excessive length, or formatting issues.

Outcome

The preview workflow enables early detection of content issues, ensuring that only well‑formed, appropriately truncated notifications are sent, thereby reducing errors and improving communication quality.

Workflow

• 1. Provide a normalized signal JSON to the Payload Builder Actor.
• 2. Specify target (slack, teams, generic) and presentation settings (includeHeadline, includeSummary, etc.).
• 3. Actor generates an unsent payload preview with content, truncation info, and delivery fields.
• 4. Inspect the preview’s content, attribution, and truncation warnings.
• 5. If acceptable, forward the payload to a sender with proper credentials; otherwise, adjust content or settings and repeat.

Evidence

The Payload Builder accepts one supplied normalized signal, 1–3 evidence references, a target shape, and seven explicit presentation settings.

Source

Inspect content and payload along with the unsent and delivery fields. The result is a preview; it does not establish delivery to Slack, Teams, or any generic webhook.

Source

Length handling is especially relevant before adding a sender. maxContentChars accepts integers from 120 to 1200. Truncation slices by Unicode code points and adds no ellipsis.

Source