Oracleoverdue_total is above 60,000Illustrative daily checks- Mon 09:0058,900.00Within the limitNo alert sent
- Tue 09:0061,480.00Limit crossedOne alert sent
- Wed 09:0063,200.00Still openNo repeat message
- Thu 09:0057,200.00Back within the limitOne recovery sent
#financeSlack
61,480.00 overdue across 7 customers.
| Customer | Overdue |
|---|---|
| Castellan Foods | 28,900.00 |
| Northgate Clinics | 17,320.80 |
57,200.00 overdue. The alert has recovered.
Slack example · Business Core and up.
Know when a number crosses the line.
Schedule reports from a saved query, or set an alert for a number that crosses a limit. Query Streams checks on your schedule and sends the result where your team already works.
In-app alerts and scheduled reports on Free.
Email from Personal Core. Slack and other business channels from Business Core.
Three things it can do with one saved query.
Start with a saved query you already trust. A rule reuses its connection and filters, with read-only execution through your Network Agent. Choose a threshold alert, a scheduled report or an optional summary written by Nova.
Databases and apps alike. Rules reuse the connectors behind your saved queries. Explore all data connectors
Tell you when a number crosses a lineData Alerts, every plan
Give a number a limit: above it, below it, a row count, or a change since the last run. While things are fine you hear nothing. When it crosses, you get one message, at the severity you chose, and one more when it is back to normal.
CSV Folderoverdue_totalOne message when it opens. One when it recovers.
Business Core and up for this external channel.
Send the figures on a scheduleReports, every plan
The schedule fires, the query runs, and the results post where you chose. Nothing to download, nothing attached: the report is the message, and every run keeps a link back to it in the portal. If you like, it can hold a run back when there is nothing to say.
MariaDB| Customer | Overdue |
|---|---|
| Castellan Foods | 28,900.00 |
| Northgate Clinics | 17,320.80 |
Daily checks on Free; faster schedules on paid plans.
Have the report written out in EnglishNova-narrated reports, Business Core and up
Nova, the built-in AI analyst, can investigate beyond the report rows with additional read-only queries on the same connection. It checks related records and trends to explain what changed, what may be behind it and what deserves attention. The figures are always built first and still send if narration is unavailable.
Supabase| Customer | Overdue |
|---|---|
| Castellan Foods | 28,900.00 |
| Northgate Clinics | 17,320.80 |
Payment history shows Castellan usually settles within 14 days, but its 28,900 is now 31 days overdue. Customer notes record an unresolved invoice dispute. This looks like a collection exception; check the dispute before sending another reminder.
Investigated: Payment history / invoice aging / customer notesBusiness Core and up · uses Nova credits.
The figures still send if narration is unavailable.
Where the message lands.
Every rule reaches the bell inside Query Streams. From there it can also go to email, to the chat tools your team already reads, or to your own system through a webhook. One rule can send to several places at once.
Discord Personal Plus and up
Slack Business Core and up
Slack-compatible Business Core and up
Google Chat Business Core and up
Telegram Business Core and up
Webhook Business Core and up
- A message built for each toolSlack, Discord, Google Chat and Telegram each get a message made for that platform. Google Chat keeps repeat notices for one rule in a single thread.
- Email you can follow up onEmail is delivered per recipient. Business Core and up add read receipts to help you follow up on reports.
- Webhooks you can trustWebhook deliveries are signed, so your receiver can check a message really came from Query Streams before acting on it.
- A link to every runEach run keeps its own page in the portal. Hand a colleague the link instead of forwarding a copy.
One query. Three setup steps.
Choose a saved query
Use a query you already have, or create one in the Query Builder. Rules reuse its connection and filters.
Pick alert or report
Choose a schedule. For an alert, set the condition to watch; for a report, choose whether to send every run or only runs that meet a condition.
Choose where it lands
Use the in-app channel on Free, or add email, chat tools and webhooks as your plan allows. Every run has its own link in the portal.
Free supports daily checks. Paid plans add faster schedules, as often as every five minutes. Compare schedules and allowances.
On every plan, including Free.
Free includes one alert rule and one scheduled report, with daily checks and one in-app delivery channel. Paid plans add more rules, faster schedules and additional delivery channels.
Questions people ask.
What is the difference between an alert and a report?
An alert checks a condition against your query's results on a schedule and only sends when the condition breaks. It then stays open until the number comes right, and you get one more message when it does. A report sends on its schedule every time and posts the results into your channels. You can still attach a condition to a report, but there it only decides whether that run is worth sending.
Can I get a sales report in Slack every Monday morning?
Yes. Make a report rule, point it at your sales query, give it a weekly schedule and pick Slack as a channel. Add email, Discord, Google Chat or Telegram alongside if different people read in different places. The bell inside Query Streams is there on every plan; Slack comes in on Business Core and up. If you also want to hear about a bad day without waiting for Monday, add a second rule as an alert with a limit on the same query.
Do I have to write new SQL to schedule a report?
No. A rule points at a saved query you already have in the Query Builder and reuses it, with its connector and its filters. There is no rule language to learn, and the rule never rewrites your query. On Business plans and up, Nova, the AI analyst built into Query Streams, can read your schema and propose both the query and the rule.
Do I get raw numbers, or something readable?
Either, per rule. The figures your query returned are always built first and always send. On Business Core and up you can switch on narration, and Nova writes a short summary in English of what is happening, comparing with earlier runs so a change arrives as a sentence. If narration ever fails, the report still goes out with the figures. Narration uses the Nova credits included in your plan, then pay as you go.
What can an alert actually check?
A limit on a value your query returns, a row count that is too high, too low or zero, or a change since the last run. So the number can be revenue, a stock level, a price, a count of failed payments, or anything else a query can produce. Each rule carries a severity of critical, warning or info. This watches the business numbers in your results; it is not a server-health tool. If you want results copied into another tool on a schedule rather than a message, that is Automation.
Can a rule watch files or SaaS data too?
Yes. Rules use saved queries, so they work with supported databases, files, logs and API-connected services. For a source that syncs data, each check reads its latest synced copy. Browse supported connectors.
Stop going to look. Let it tell you.
One alert rule and one report are on every plan, including Free. See what each plan adds.
English 
Spanish 
German 
French 
Portuguese 
Japanese 
Korean 
Chinese 
Italian 
Dutch 
Indonesian 
Polish