DATA OPS
Validate webhook-posted CSV and append clean rows to BigQuery
Accepts a CSV via HTTP webhook, validates it against a column contract, appends valid rows to a BigQuery table, and returns a rejection report listing every bad row to the caller.
How it runs
The automated pipeline, trigger to output.
- TriggerCSV posted to HTTP webhook endpointHTTP webhook
- ActionParse CSV and validate against column contract
- LogicPartition into accepted vs rejected rows
- ActionAppend accepted rows to BigQuery tableBigQuery
- OutputReturn rejection report in webhook responseHTTP webhook
What it does
Exposes an HTTP endpoint that partners or internal services POST a CSV to. Each upload is validated against a defined column contract, valid rows are appended to a BigQuery table, and the endpoint responds synchronously with a structured report of which rows were rejected and why.
When to use it
Use it when you want a self-serve CSV intake that gives the uploader immediate feedback instead of failing silently downstream. Good for vendor portals, internal tools, or any integration where the sender needs to know exactly which rows to fix and resend.
How it works
- 1An HTTP webhook receives a POST containing the CSV payload.
- 2The pipeline parses the file and checks headers, types, and constraints (ranges, enums, non-null) row by row.
- 3A logic step partitions rows into accepted and rejected, tagging each rejected row with a reason.
- 4Accepted rows are streamed into the target BigQuery table via an insert job.
- 5The webhook response returns counts plus the full rejected-row report so the caller can correct and retry.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.