DATA OPS
Block HubSpot Segment Sync on Size-Drift Anomaly
Compares today's computed segment size against the recent baseline and halts the HubSpot writeback if the count swings beyond a safe threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires after segment table refresh
- ActionQuery current count and rolling baseline from BigQueryBigQuery
- LogicCompute drift and compare against allowed band
- ActionIf within bounds: sync segment to HubSpotHubSpot
- OutputIf out of bounds: post drift alert to Slack and skip syncSlack
What it does
A broken upstream join or a bad filter can shrink a segment from 50,000 contacts to 50 overnight — and a naive sync would happily overwrite the whole list in HubSpot. This workflow guards against that by checking segment size against a rolling baseline before any writeback happens, blocking the sync when the change is too large to be real.
When to use it
Use it for any high-stakes HubSpot list or property writeback where a sudden swing in row count signals an upstream data break rather than a legitimate change. It is your circuit breaker against silent segment collapse.
How it works
- 1A schedule triggers after the segment table refreshes.
- 2Query the current segment count and the stored rolling baseline from BigQuery.
- 3A logic step computes drift and compares it to the allowed percentage band.
- 4If drift is within bounds, sync the segment to HubSpot and update the baseline.
- 5If drift exceeds bounds, skip the sync and raise an alert in Slack with the before and after counts so a human can decide.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect HubSpotCRM, deals, marketing, support.
- 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.