Real-time Alerts and Signals

Real-time Usage and Revenue Alerts and Signals

Amberflo can send alerts and signals via email and webhooks.

A signal can be defined on a specific customer, or on all customers.
A signal rule can be defined as exceeding a constant number or a percentage change of metered data over time.
Signals can be defined on billing data as well to enable valuable alerts to customers, sales teams, and finance teams.

Signal examples:

  1. Get an email for any customer that exceed 1000 hours per week.
  2. Get a slack message for any customer that used 20% less week over week.
  3. Account manager receives email whenever customer usage surpasses amount of prepaid credits in Wallet.
  4. Head of Finance receives email alert when 25, 50, 75, and 90 percent of quarterly revenue target is reached.

See API Reference for Signals

The easiest way to configure Alerts & Signals is via the Console.


Realtime vs Scheduled

A realtime signal is evaluated every 5 minutes. It filters out active customers based on recent usage. If a signal condition is met for a given customer, an alert will be fired. Then alerts for this customer are suspended for an hour to prevent spam. All billing and revenue related signals are realtime.

A scheduled signal runs on a schedule which can be specified using a cron expression. See cron examples. This type of signal is best for running usage queries periodically.

Customer selection

A signal can be defined on a specific customer or on all customers.

Email and Webhooks

When a signal rule is satisfied, it can send an alert as an email or calling a web hook or both. A web hook payload and headers can be customized using context variables. See Signal Webhooks

Sample email:


Sample web hook for Slack:


What’s Next