DATA OPS
Fivetran schema-change webhook triage to ClickUp or auto-approve
Receives Fivetran schema-change webhook events, auto-approves additive changes, and routes destructive changes to a ClickUp ticket with a Slack heads-up for human review.
How it runs
The automated pipeline, trigger to output.
- TriggerFivetran schema-change webhook receivedHTTP webhook
- LogicParse payload for change type and columns
- LogicBranch additive auto-approve vs destructive review
- ActionOpen ClickUp ticket for destructive changeClickUp
- OutputPost Slack alert linking the ticketSlack
What it does
Reacts to schema-change events the moment a connector reports them, rather than polling on a timer. When Fivetran (or any loader) posts a schema-change webhook, this inspects the payload, lets harmless additive changes flow through automatically, and quarantines destructive ones into a ClickUp ticket for a human to approve before they propagate.
When to use it
Use it when your loader emits schema-change webhooks and you want near-real-time triage — fast-tracking the safe 90% while pausing the risky 10% for review, instead of treating every change the same.
How it works
- 1An incoming HTTP webhook trigger receives the schema-change event.
- 2Parse the payload to extract the table, change type, and affected columns.
- 3Branch on change type: additive (new column or table) vs destructive (drop, type narrow).
- 4For additive changes, log the event and exit — auto-approved.
- 5For destructive changes, open a ClickUp ticket capturing the full payload and proposed action.
- 6Post a Slack alert linking the ticket so a reviewer can approve or block.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 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.