Operations
Weekdays at 7:00amAsk your database a question every morning.
A workflow reads your schema, writes the SQL, runs it, checks the results in its sandbox, and posts a report to the channel your team reads.
5,000 free credits to start.
How it works
Three steps to a workflow
- Step 01
Connect your database
Add a Postgres, MySQL, or ClickHouse connection with read-only credentials. Reach a private database through an SSH tunnel so nothing is exposed to the internet.
- Step 02
Describe the report
Say what the team wants to know and what counts as unusual. The agent reads the schema, writes the queries, and shows the SQL it ran next to the answer.
- Step 03
Put it on a schedule
Describe the cadence in plain words. Helios turns it into a cron expression. The report shows up before standup every day.
The run
What one run looks like
Each line is a tool call. The agent finds the API it needs, reads the result, and acts. The full transcript stays on the run.
Each morning, post yesterday's metrics with anything unusual called out.
- clickhouse·read the schema and query 24h of events
- postgres·join account metadata
- code·compute trends and flag outliers
- slack·post the report to #metrics
Metrics · Mar 6
- Runs 41.2k · up 6% day over day
- Signups 128 · in line with the trend
- Error rate up 0.4pp, concentrated in one region
- Queries and assumptions attached to the run
Templates
Start from a prompt that works
Each template has the prompt, the trigger it needs, and the integrations it uses.
Operations
Weekly metrics report
Queries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.
Operations
Nightly data quality checks
Runs your invariants against production every night and emails the on-call analyst which rows broke and since when.
FAQ
Questions, answered
Put a workflow on database reporting.
Write the prompt, pick the trigger, and read the first run.