DATA OPS
Webhook CSV Intake with Inline Validation and Rejection Response
Accepts a partner CSV upload over a webhook, validates it synchronously, and responds with an accept/reject verdict.
How it runs
The automated pipeline, trigger to output.
- TriggerPartner POSTs CSV to webhookHTTP webhook
- LogicParse and validate rows against schema contract
- LogicBranch accepted rows from rejected rows
- ActionInsert accepted rows into PostgresPostgres
- ActionArchive rejected rows + defect report to S3AWS S3
- OutputReturn JSON verdict in webhook responseHTTP webhook
What it does
This workflow exposes a webhook that partners POST their CSV to. It validates the payload against your contract schema on the spot and returns a structured verdict in the HTTP response: how many rows were accepted, how many were rejected, and the exact reason for each rejection. Clean rows are committed to Postgres and the quarantined rows are archived to S3 for audit.
When to use it
Use it when partners integrate programmatically and need immediate feedback rather than an out-of-band email hours later. The synchronous response lets their system retry or correct the feed in the same call.
How it works
- 1A partner POSTs a CSV to the webhook endpoint, firing the trigger.
- 2Rows are parsed and validated against the schema contract.
- 3The flow branches accepted rows from rejected rows.
- 4Accepted rows are inserted into the Postgres staging table.
- 5Rejected rows and a defect report are archived to an S3 quarantine prefix.
- 6The webhook responds with a JSON verdict listing counts and per-row failure reasons.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect AWS S3Buckets, objects, signed URLs.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.