CLOUD INTEGRATION

Slack Cost Alerts: Bills and Anomalies Straight to Your Channel

Clouds won’t push bills or anomalies to Slack, and DIY Incoming Webhooks mean Block Kit plus rate limits. Mof ships built-in Slack cards, pick-and-go — bills, budgets, anomalies and digests, with batching and quiet hours, no webhooks.

Documentation

Slack · wire it up yourself

Incoming Webhook

Block Kit cards

Multi-channel

Rate limits

The cloud won’t push cost — Block Kit cards are on you, and sends get rate-limited

Mof · check a box

Pick a channel

Set rules

Cards delivered

Bills / anomalies

Clean cards

Batched & quiet

Routed by channel

Built-in cards — no webhooks or APIs

Why teams use Mof to push cloud cost to Slack

Your team lives in Slack, but clouds rarely push bills or cost anomalies there — at most email. Wire up an Incoming Webhook and you’re writing Block Kit cards, configuring per workspace and channel, and handling Slack’s send-rate limits — and it still spams one message at a time.

Mof is a FinOps platform for teams running more than one cloud. It makes Slack notifications work out of the box — bills, budgets, anomalies and scheduled digests as clean cards, with batching, quiet hours and team routing, no webhooks or Block Kit.

Ways to get cost into Slack — each with a catch

Cloud-native, DIY webhook, script relay — each gets a message through, but all mean cards, rate limits and no routing.

Cloud-native notifications

No bill / cost pushAt most email, never Slack
Thresholds onlySpikes and trends go undetected
You watch the consoleNobody tells you when cost moves

DIY Incoming Webhook / app

You build Block KitCard JSON schema, fiddly to debug
Per-workspace × channelA pile of webhooks and tokens to maintain
Hits rate limitsSlack rate-limits sends; raw pushes get throttled

Third-party / script relay

Scripts / iPaaSDIY cron relays, high upkeep
Fails silentlyExpired keys or API changes break it quietly
No routing / summaryRaw fields, no team split

How Mof solves these

Built-in cards, pick-and-go — bills, anomalies and digests delivered, with batching, quiet hours and team routing.

The cloud won’t push bills and anomalies into the Slack your team lives in

Mof has built-in Slack delivery: bill updates, budgets and anomaly results land straight in a channel / DM — no more console-watching.

Rich cards are hard — Block Kit is a complex JSON schema you write and debug in code

Mof ships clean cards out of the box; pick a channel and go — no webhooks, Block Kit or APIs to touch.

Slack rate-limits sends, and every workspace / channel needs its own webhook

Mof handles connection and rate limits and batches before sending — no limits tripped, no pile of webhooks.

Raw webhooks spam — one message per anomaly, scrolled past by everyone

Mof batches, summarizes, respects quiet hours and dedupes — it says what matters without flooding.

Cloud-native offers fixed budget thresholds only, so spikes and trends surface late

Mof’s anomaly detection (Holt-Winters) catches spikes and trends and pushes early — no waiting on a dead threshold.

Even when it pushes, it’s raw fields — you can’t tell where the increase is

Mof pushes a readable summary (how much it rose, mainly driven by what) with a dashboard link to drill down.

You can’t route different bills to different owners by team / project

Mof routes by account / team / project to the right channels, and can schedule daily / weekly cost digests to a channel.

DIY webhook vs Mof

Dimension	DIY webhook	Mof
Bill / cost push	Basically none	Built-in: bills / budgets / anomalies
Message cards	Block Kit, write code	Built-in cards, pick and go
Rate limits / setup	Handle limits and many webhooks	Handled on platform, batched
Multi-cloud	Per-cloud, per-channel setup	Configure once, push across clouds
Anomaly detection	Fixed thresholds only	Holt-Winters spikes / trends
Routing	Hard to split by team	Route by account / team / project
Scheduled digests	Write your own cron	Built-in daily / weekly digests
Readability	Raw fields	Readable summary + dashboard link
Maintenance	Maintain webhooks / tokens	Platform-maintained, no ops

Slack cost notifications FAQ

What Slack notifications does Mof support?

Bill updates, budget alerts, anomaly detection results, and scheduled daily / weekly cost digests — delivered to Slack channels via Incoming Webhook or a Slack App. Content is a clean card with key numbers and a dashboard link.

Do I need to write Block Kit cards?

No. Mof has built-in Slack cards — just pick channels and set rules. No Block Kit JSON, and no rate limits or tokens to maintain.

Will it spam the channel or hit Slack’s rate limit?

No. Mof batches, summarizes, respects quiet hours and dedupes — merging related changes into one clear summary, without tripping Slack’s send-rate limits.

Can it route to different channels by team / project?

Yes. Mof routes cost and anomalies by account / team / project to the matching channel or owner.

How do I connect Slack? Is it safe?

Configure a Slack Incoming Webhook or install a Slack App. Mof uses it only to push cost messages — it doesn’t read your chats and needs no write access.