Billing Alerts Settings
Spend alert switches at 80 and 100 percent of plan, a hard-cap option with stated consequence, and a recipient email field.
Spend alert switches at 80 and 100 percent of plan, a hard-cap option with stated consequence, and a recipient email field.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Billing Alerts Settings is the spend alert panel, two threshold rows with Switches (Alert at 80% of plan on by default, Alert at 100% of plan on by default), a hard-cap section with its consequence stated plainly (at the cap overage features pause, your account stays active and core access is unaffected), and a recipient field pre-filled with billing@acme.com. The cap detail row expands when the Switch is turned on: API calls that would generate overage return a 429 and features resume at the start of the next billing cycle.
Alert thresholds and the recipient are useState; the hard-cap panel is conditionally rendered so the consequence text is only visible when the feature is active. The footer tip (use a shared inbox so the whole finance team sees alerts) is the copy that prevents a personal inbox becoming the single point of failure.
Reach for this block on the billing tab of a settings shell, wired to your billing provider and a webhooks or email alerts endpoint. Wire the recipient field to your billing contact model, not the signed-in user.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the usage alert configuration panel. Other variants:
Tip: stating the hard-cap consequence up front (pause, not cancel) is the copy that stops support tickets from panicked admins who turned it on without reading.