DATA OPS
Consent-and-PII Gate Before Salesforce Lead Writeback
Webhook-triggered guard that screens enriched leads for missing consent flags and invalid PII before upserting to Salesforce.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives enriched lead batchHTTP webhook
- LogicValidate consent flags, PII formats, required fields
- ActionWrite failing records to Postgres quarantine with reasonsPostgres
- ActionUpsert passing records to SalesforceSalesforce
- OutputPost written-vs-held digest to SlackSlack
What it does
When an enrichment job emits new or updated leads, this workflow acts as a compliance and quality gate before they touch your CRM. It verifies each record carries a valid consent flag and well-formed contact PII, upserts only the clean ones to Salesforce, and parks the rest in a quarantine table with the exact rule that failed.
When to use it
Use it when leads arrive from a reverse-ETL or enrichment pipeline and you cannot risk writing unconsented or malformed contacts into Salesforce — where bad records trigger compliance exposure and pollute sales workflows downstream.
How it works
- 1A webhook fires when the enrichment pipeline emits a batch of lead records.
- 2A validation step checks consent flags, email and phone formats, and required fields per row.
- 3Records failing any rule are written to a Postgres quarantine table with a failure reason.
- 4Passing records are upserted to Salesforce.
- 5A Slack digest reports how many leads were written versus held and why.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Snowflake column type-drift sentinel with Linear fix ticket
Snapshots the data types of every column in your tracked Snowflake schemas on a schedule, diffs against the last snapshot.
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.
BigQuery dropped/renamed column sentinel with PagerDuty incident
Detects when a column is dropped or renamed in your governed BigQuery datasets and, because that breaks downstream queries hard, pages the on-call via PagerDuty and posts…
PR-time Snowflake schema contract check on dbt model changes
When a pull request changes a dbt model, it compares the model's declared output columns against the live Snowflake table it will replace and blocks the merge with a GitHub check…
Agent-triaged warehouse drift with impact analysis and runbook update
On a webhook from your warehouse audit log, an agent investigates the changed column, traces which downstream models and dashboards depend on it.
Cross-warehouse replication schema mismatch reconciler
Compares the column shape of mirrored tables between BigQuery and Snowflake and, when a replicated table has drifted out of sync between the two, opens an Asana task for the data…
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.