DATA OPS
Booth-scan to CRM reconciliation and lead dedup
Daily, finds booth-scanned attendees with no matching Salesforce record, dedupes against existing contacts by email and company, creates clean leads for true gaps.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule after scan sync
- ActionRead unreconciled scans from AirtableAirtable
- ActionMatch scans to Salesforce by email and domainSalesforce
- LogicBranch into known, duplicate, or new
- ActionCreate event-sourced leads in SalesforceSalesforce
- OutputQueue duplicates and post summary to SlackSlack
What it does
This closes the gap between who you scanned and who exists in the CRM. It reads the day's scans from Airtable, attempts an email-and-company match against Salesforce, and splits results into already-known contacts, fuzzy duplicates that need a human merge, and genuinely new attendees. New attendees become clean Salesforce leads stamped with the event source; possible duplicates are queued in Airtable for review. A summary goes to Slack.
When to use it
Use it the morning after each event day so booth scans become attributable CRM records before sales follows up, instead of letting unmatched scans silently rot in a spreadsheet.
How it works
- 1A daily schedule fires after scans land in Airtable.
- 2Read new, unreconciled scans from Airtable.
- 3Match each scan to Salesforce by email and company domain.
- 4Branch scans into known, possible duplicate, or new.
- 5Create event-sourced leads in Salesforce for the new attendees.
- 6Queue possible duplicates in Airtable and post a reconciliation summary to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect AirtableBases, tables, views, automations.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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 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 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…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
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.