Data
Give your agents full access to your databases.
Connect Postgres, MySQL, or ClickHouse and agents introspect the schema, write real SQL, and reason over the results in their own sandbox. Reach private databases through an SSH tunnel without opening anything to the internet.
Capabilities
What agents do with Databases
Agents introspect your schema, write real SQL, and reason over the results in their own sandbox, with credentials handled server-side.
- Connect Postgres, MySQL, and ClickHouse with credentials stored envelope-encrypted.
- Introspect schemas — tables, columns, types, keys, and indexes — before writing a query.
- Write and run SQL against your data, then analyze results in the sandbox with code.
- Reach private databases through an SSH tunnel, so nothing needs public exposure.
- Grant read-only credentials so a reporting agent can never write.
- Memory carries what an agent learns about your schema from one run to the next.
Use cases
Tasks you can hand to a database agent
Ask your database a question in English
The agent reads the schema, writes the SQL, runs it, and explains the answer — including the caveats in the data.
Which accounts grew usage more than 50% last month, and what do they have in common?
- postgres·introspect schema for usage tables
- postgres·query month-over-month usage by account
- code·cluster the growing accounts by attributes
23 accounts grew over 50%
- 18 connected a second integration last month
- Median team size 12, up from 7
- Query and assumptions included in the run
Publish a metrics report on a schedule
Every morning the agent runs the queries, computes the derived metrics, and posts a report your team reads instead of a dashboard nobody opens.
Each morning, post yesterday's metrics with anything unusual called out.
- clickhouse·query events for the last 24h
- postgres·join account metadata
- code·compute trends and flag anomalies
- slack·post 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
Run data quality checks every night
The agent checks the invariants you care about, and when one breaks it says which rows, since when, and what changed upstream.
Nightly, run our data quality checks and alert on failures.
- postgres·run 14 invariant checks
- postgres·isolate failing rows and first occurrence
- resend·email the on-call analyst
2 checks failed
- `orders.currency` null on 41 rows since 02:10
- `accounts.plan` has 3 values outside the enum
- 12 checks passed
Move data where it needs to be
Query results become CRM fields, spreadsheet rows, or an email. The agent handles the shape change in code.
Nightly, sync product usage into the CRM as account health fields.
- postgres·compute 30-day usage per account
- code·map usage into health tiers
- attio·update 480 account records
480 accounts synced
- 31 moved into `at risk`
- 18 flagged as expansion candidates
Cross-app recipes
Your databases work alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
Templates
Ready-to-run database agents
Copy the prompt, connect your tools, and put an agent on the task.
Sales & RevOps
Churn risk watchlist
Joins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.
Sales & RevOps
Onboarding email that reads the account
Checks what each new account has actually set up and sends the message that helps them next, rather than the next message in a sequence.
Operations
Weekly metrics report
Queries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.
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.
Use cases
Where database agents earn their keep
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.
Email outreach
An agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.
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.
FAQ
Questions, answered
Put an agent on your databases.
Connect it once, describe the task in plain English, and let it run on your schedule or your events.