BigQuery Metrics Digest with Hermes
The seductive failure is a sentence explaining why the number moved. A result set can tell you what changed and it can never tell you why, and a digest offering a reason gets believed. Hermes reasons capably, which is exactly why the instruction is to attach no reason to any movement and to report an outlier with both numbers and nothing more.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Morning metrics 12 August
All seven queries returned inside nine seconds. Daily active users came back at 41,208 against 39,940 yesterday, checkout conversion at 2.31 percent against 2.44, new paid signups at 186, and refunds at 12,340.55 BRL. The events query scanned 84 GB, in line with every other morning this month.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Google BigQuery
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Metrics queries
The exact SELECT statements to run each morning, each with the name it should carry in the digest. Include the partition filter every table needs, because the agent adds nothing to what you write, and this list is the only SQL it will ever run.
Digest style
How the digest should read - which metric leads, what counts as an outlier worth flagging (checkout conversion under 2 percent, refunds above 5,000), and who to tag when a query fails.
Runs on Hermes
Preselected for this page — connect your Hermes account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Hermes for this agent
What changed, not why
An outlier is one line carrying both values. The explanation is a conversation among people who know what shipped yesterday.
Zero printed as zero
When last night's partition never landed, the metric returns zero and the digest prints zero beside yesterday's real number. That contrast is usually the fastest warning that an upstream job died.
Before you fork
Will it tell me why a number moved?
No, and it should not. It reports the value and the day on day difference, and any theory about a broken pipeline or a marketing push comes from whoever reads it. That is a genuine limitation if you wanted analysis, and it is what keeps a coincidence from being posted as a cause every morning.
Run it with a different agent
Put BigQuery Metrics Digest to work on Hermes
Free to start. Guided setup, a test run against staged conversations, and it's live.