CLOUD INTEGRATION

Lark Cost Alerts: Bills and Anomalies Straight to Your Channel

Clouds won’t push bills or anomalies to Lark, and DIY custom bots mean card JSON plus signing and rate control. Mof ships built-in Lark cards, pick-and-go — bills, budgets, anomalies and digests, with batching and quiet hours, no webhooks.

Documentation

Lark · wire it up yourself

Bot webhook

Card JSON

Cron scripts

Key upkeep

Clouds won’t push cost data — and hand-built cards spam easily

Mof · check a box

Pick a channel

Set rules

Cards delivered

Bills / anomalies

Rich cards

Batched & quiet

Routed by channel

Built-in cards — no webhooks or APIs

Why teams use Mof to push cloud cost to Lark

Your team lives in Lark, but clouds rarely push bills or cost anomalies there — at most SMS or in-console. Wire up a custom bot and you’re assembling interactive-card JSON, handling signing and rate control, and configuring per cloud and per group — and it still spams one message at a time.

Mof is a FinOps platform for teams running more than one cloud. It makes Lark 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 card JSON.

Ways to get cost into Lark — each with a catch

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

Cloud-native notifications

No bill / cost pushAt most SMS or in-console, never Lark
Thresholds onlySpikes and trends go undetected
You watch the consoleNobody tells you when cost moves

DIY custom-bot webhook

Interactive cards are complexLark card JSON schema, tuned in the card builder
Signing + rate controlSignature verification and send-rate limits to handle
Per-cloud × per-groupA pile of webhooks and keys to maintain

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, routing and no JSON.

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

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

Rich cards are hard — Lark interactive cards are a complex JSON schema you tune in the card builder

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

Custom bots need signature verification and rate control — more code to write yourself

Mof handles connection, signing and rate control and batches before sending — no limits tripped, nothing to maintain.

Per-cloud × per-group webhooks are repetitive, messy at scale, and keys need upkeep

Mof is configured once, pushes across all clouds, and routes to the right groups / topics — maintained on the platform side.

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 groups, and can schedule daily / weekly cost digests to a group.

DIY webhook vs Mof

Dimension	DIY webhook	Mof
Bill / cost push	Basically none	Built-in: bills / budgets / anomalies
Message cards	Card JSON in the builder	Built-in cards, pick and go
Signing / rate control	Handle signing and send limits	Handled on platform, batched
Multi-cloud	Per-cloud, per-group webhooks	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 / keys	Platform-maintained, no ops

Lark cost notifications FAQ

What Lark notifications does Mof support?

Bill updates, budget alerts, anomaly detection results, and scheduled daily / weekly cost digests — delivered to Lark custom bots or app bots. Content is a clean interactive card with key numbers and a dashboard link.

Do I need to write Lark card JSON?

No. Mof has built-in Lark interactive cards — no card-builder JSON, no signing or rate control to handle. Just pick channels and set rules.

Will it spam the channel or trip Lark’s rate control?

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

Can it route to different groups by team / project?

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

How do I connect Lark? Is it safe?

Configure a Lark custom-bot webhook or internal app. Mof uses it only to push cost messages — it doesn’t read your chats and needs no write access.