Slack integration
FlowSprite events arrive as HMAC-signed webhooks with automatic retry. Point one at a Slack incoming webhook or workflow and you have channel notifications for the events that matter — no firehose.
What you get pinged about
Metadata sync completed or failed
A sync.completed or sync.failed event fires when your org mirror updates — or when the sync breaks and needs a look.
Deploy kicked off
A deploy.started event fires when a change starts down the deploy path. Click through to the PR for the result.
PRs, via GitHub
FlowSprite changes are ordinary pull requests, so GitHub's own Slack app announces them — opened, reviewed, merged — with no extra wiring.
How it actually connects
Every event is delivered as a signed, verifiable HMAC webhook with retry and backoff — the same mechanism whether the destination is Slack or any endpoint you run. To land events in a channel, point the webhook at a Slack incoming webhook or a Slack workflow that accepts inbound HTTP requests. A native FlowSprite Slack app — one-click install, in-Slack approvals — isn't shipped yet.
Wire up your first webhook
Generate a signed webhook URL from your dashboard, point it at Slack.
Start free in 2 minutes