Skip to content
ADVISORY RECONCILIATION · STRIPE ↔ ENTITLEMENTSRun the browser-only CSV audit

INTEGRATION · SLACK

Findings should reach the team that owns them.

Route high-priority findings to a Slack channel. Only hooks.slack.com URLs under /services/ are accepted. Test before you trust.

How it works

Save a Slack incoming webhook URL as an alert destination. When reconciliation finds high-priority open findings, alerts-dispatch sends a formatted message to the channel.

  • Only hooks.slack.com URLs under /services/ are accepted
  • Validation at save time and send time
  • Test send from the alerts page
  • Delivery recorded in alert_history

Security

Webhook URLs are stored as destination metadata. SSRF guards block private IPs, localhost, and non-HTTPS destinations. The host must be on the allowlist or be hooks.slack.com.

Frequently asked

Can I send to multiple channels?

Each alert destination is one configuration. You can create multiple destinations for different channels.

What triggers an alert?

High-priority open findings that have not already been alerted within the deduplication window.

Next step

Start with the evidence. Connect nothing until the workflow earns it.

START WITH THE EVIDENCE

See the gap before it becomes a refund.

Run a private CSV audit in your browser, or create a workspace and connect an isolated Stripe TEST account.