CAST AI Webhook Notification Lane

Overview

Route only actionable CAST AI notifications to a hardened receiver. Treat the console-configured request template as the payload contract and the CAST AI Audit log as reconciliation evidence, not as a guessed public event schema.

Prerequisites

• CAST AI organization, notification owner, severity policy, and receiver
• HTTPS endpoint with authentication, request limits, retention, and on-call ownership
• Sanitized sample template and failure fixture

Instructions

Step 1: Define the event contract

Use Read and Grep to identify required severity levels, cluster and organization scope, destination, payload fields, privacy classification, deduplication key, and escalation behavior. Exclude fields the receiver does not need.

Step 2: Harden the receiver