Alerts and reports
You shouldn't have to open a dashboard to find out something moved. Axiome watches your numbers and sends you a Slack message — either when a value crosses a limit you set, or on a schedule you choose.
There is one thing to create, an alert, and it comes in two types:
| Type | Fires when | Use it for |
|---|---|---|
| Threshold | A value crosses the limit you set | "Tell me if revenue drops below 10 000." |
| Report | Every time the schedule comes round, no condition | "Send me our KPIs every Monday at 9." |
Threshold alerts are covered in Threshold alerts, reports in Scheduled reports.
Before you start: Slack
Alerts are delivered to Slack, so your workspace needs a Slack workspace connected first. If it isn't, Axiome tells you:
Connect Slack first — Alerts are delivered to Slack. Connect a workspace to start creating them. If you're not an admin, ask one to connect it.
Connecting Slack is an administrator task, done once — see Slack integration if that's you.
Once connected, each alert goes to a Slack channel of your choice, or to you privately with Send me a direct message.
Three ways to create one
From the dashboard's Alerts panel — click the bell in the left sidebar of any dashboard. You get every alert on that dashboard, grouped, with its status, schedule, and last delivery. Click New alert and pick what to watch.
From a component's bell — in Edit mode, KPI cards and charts have a small bell in their control rail. It opens a short list of that component's alerts and a create form already pointed at it. The bell turns amber when the component has an active alert.
By asking Axi — the fastest route. Just say what you want:
"Alert me when revenue drops below 10k" "Send an AI summary of this dashboard to #direction every Monday"
Axi creates the alert, and can also list, edit, or delete your existing ones.
Reading the panel
Each alert in the panel shows:
- A status dot — green (all good), amber (currently triggered), red (failing), grey (disabled).
- A Report or Threshold badge.
- Its frequency — Daily at 09:00, Monday at 08:30, Monthly on the 1st at 07:00…
- Last fired, or never.
- A switch to pause it, a pencil to edit, a trash to delete.
Alerts are grouped by what they watch: per component, Entire dashboard, and AI summaries. A fourth group, Removed widget, collects alerts whose component has since been deleted — edit them to point somewhere else, or delete them.
Good to know
- A threshold alert notifies you once. When the condition trips, you get one message. You won't be pinged again while it stays tripped, and it quietly re-arms once the value comes back to normal — so a metric sitting below its limit for a week doesn't flood your channel. There's no "back to normal" message.
- Reports always send, on schedule, regardless of the numbers.
- Test before you trust it. The editor has a Test button that runs the alert immediately and posts a real (marked) Slack message. It doesn't disturb the schedule.
- Anyone can create alerts — this isn't reserved for administrators.
- A workspace can have 20 alerts switched on at once. Paused ones don't count, so there's no limit on how many you keep around — only on how many are actively running. Past the limit, creating or re-enabling an alert fails and you'll need to turn one off first.
- Pausing beats deleting when you just want a break: the switch keeps the configuration, and frees a slot against the limit.
- If an alert breaks (its component was deleted, its data source went away), Axiome posts a warning in the same channel after a few failed attempts, so it never fails silently.
If you'd only want to know when something happens → threshold. If you want the number in front of you regularly, whatever it says → report. Plenty of teams run both on the same KPI.