Skip to content

PopSQL: limited support.

Migrate now →
DataRunner
Start free

Documentation

How DataRunner works, without decoration.

What the product does today, in the order you will need it. Nothing here describes a planned feature.

01

Start

Getting startedFrom signup to the first delivered report, in the order the screens appear.
ConnectionsWhich databases are supported, what each one can actually do, and how credentials are stored.
QueriesThe SQL workbench, parameters, versions, and what happens when a result is too large.
AI assistantConnecting your own model, asking in plain language, and what the product lets the answer touch.
02

Automate

SchedulesCron, per-schedule timezones, run history, and what happens when a run fails.
Reports and deliveryOutput formats, recipients, and the rules that decide whether a send happens at all.
ChannelsThe nine delivery destinations, what each one needs, and what each one can carry. Each has its own page with the setup, the fields and how to test.
Command lineInstall it, authenticate, and turn a query into a build step.
03

Watch

Endpoint monitorsHTTP and database checks, what counts as an outage, and how an incident is born.
Hosts and the agentWhat the agent collects, how it enrolls, and why it cannot read your database.
Alerts, incidents and statusWhere an alert goes, how to silence a maintenance window, and what the public sees.
04

Govern

Security and dataEncryption, roles, authentication, audit, and what you can export or delete.
05

Data

Dashboards and sharingPanels built from queries, per-dashboard filters, public links with password and expiry, and the iframe.
Catalog, metrics and data qualityDescribe columns, define a metric once, and test every run against freshness, null and uniqueness contracts.
Pipelines, syncs and notebooksChain queries with stop-on-failure, copy results out, and explore in cells.
06

People

Contacts and listsWhere contacts come from, custom fields, spreadsheet import, lists with segments, and unsubscribes.
CampaignsOne send to lists, over e-mail, WhatsApp or Telegram, with a template, variables, tracking — and what has to be in place before the first one leaves.
SequencesA series of messages with a wait between them, started by manual enrollment, by a form, or by the API.
FormsA public form hosted by the API, with optional captcha, that records the submission and can create the contact and subscribe it to a list.
07

Publish and integrate

Status pages and SLOsA public page tied to your monitors, with incidents, e-mail subscription, a custom domain and availability targets.
API, keys and outbound webhooksThe browsable reference, how to authenticate with a key, and the events the product pushes to your endpoint.
08

Account

Plans, billing and accountMonthly or yearly, what happens when the card fails, extra workspaces, ownership and a confirmed e-mail.
09

Delivery channels

EmailWiring up Email: what to create at the provider, what to paste here, what goes in Target, and how to test before depending on it.
WhatsAppWiring up WhatsApp: what to create at the provider, what to paste here, what goes in Target, and how to test before depending on it.
TelegramWiring up Telegram: what to create at the provider, what to paste here, what goes in Target, and how to test before depending on it.
Generic webhookWiring up Generic webhook: what to create at the provider, what to paste here, what goes in Target, and how to test before depending on it.
SlackWiring up Slack: what to create at the provider, what to paste here, what goes in Target, and how to test before depending on it.
DiscordWiring up Discord: what to create at the provider, what to paste here, what goes in Target, and how to test before depending on it.
PagerDutyWiring up PagerDuty: what to create at the provider, what to paste here, what goes in Target, and how to test before depending on it.
OpsgenieWiring up Opsgenie: what to create at the provider, what to paste here, what goes in Target, and how to test before depending on it.