Operations
Weekly metrics report
Queries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.
The prompt
This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
Every Monday at 7am, query our ClickHouse events table and our Postgres accounts table to build last week's metrics: signups, activated accounts, weekly active accounts, total runs, revenue, and churn. Compute week-over-week and four-week trends for each. Then look for anything unusual — a metric outside its recent range, a sudden concentration in one region or plan tier, a metric that moved in the opposite direction from its usual correlate — and explain what you found. Post to #metrics with the headline numbers first, then the anomalies, then a short note on what you checked and found normal. Include the SQL you ran as a thread reply.
Trigger
What starts this agent
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
Integrations required
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
Metrics · week of Mar 3
- Signups 1,204 · up 8% week over week
- Net revenue retention 112%
- Error rate up 0.4pp, concentrated in one region
New to Helios? Start with Run your first agent.
Use cases
The task behind this template
Database reporting
An agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads — instead of a dashboard nobody opens.
Billing operations
An agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.
Weekly digests
An agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.
CRM data sync
An agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.
Related templates
Pair it with these
Operations
KPI sheet refresh
Pulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.
Operations
Nightly data quality checks
Runs your invariants against production every night and tells the on-call analyst which rows broke and since when.
Sales & RevOps
Churn risk watchlist
Joins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.
Run Weekly metrics report on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.