← All templates

Operations

Nightly at 3:00am

Nightly data quality checks

Runs your invariants against production every night and emails the on-call analyst which rows broke and since when.

5,000 free credits to start.

The prompt

The workflow prompt

Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger.

prompt.md
Every night at 3am, run our data quality checks against the production Postgres replica.Check that no order has a null currency, every account's plan is one of the four values in our enum, no invoice has a total below zero, every user row has a matching account, and the events table has received rows in each of the last 24 hours.For every failing check, find how many rows are affected, identify the earliest affected row and its timestamp, and look at what changed upstream around that time.Email the on-call analyst through Resend with only the failures, the affected row counts, the first occurrence, and the query you ran.When everything passes, send nothing.

Trigger

What starts this workflow

Nightly at 3:00am

Runs on a schedule. Describe the cadence in plain words and Helios writes the cron expression. Schedules run in UTC.

Integrations it uses

Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token.

Example output

What you get back

Every run keeps its full transcript. The steps the agent took, each tool call, and the result.

2 checks failed

  • `orders.currency` null on 41 rows since 02:10
  • `accounts.plan` has 3 values outside the enum
  • 12 checks passed

New to Helios? Start with Run your first workflow.

Run Nightly data quality checks on your tools.

Connect the integrations, paste the prompt, and pick the trigger.