There is no judgement in this job at all. Run the list, transcribe what came back, name what broke, post once. OpenClaw is an open agent well suited to a task with edges that hard, and the harness runs hosted, so the digest lands at 08:00 without anybody owning a scheduler.
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.
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 OpenClaw
Preselected for this page — connect your OpenClaw 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.
The result set is the digest. No ratio it worked out, no weekly total, no projection, and no yesterday's figure standing in where today's is missing.
The timing, the harness and the credentials all sit in NoClick. Nobody is on the hook for a cron job that quietly stopped in March.
Yes. It needs a Google Cloud credential with Data Viewer on the datasets and Job User on the project, a Slack channel, and your query list. The SQL is the analyst's own work, which is rather the point. The only thing worth asking a platform team for is a project quota if you want a spend ceiling.
Free to start. Guided setup, a test run against staged conversations, and it's live.