DATA OPS
RMA Defect-Pattern Watch and Alert
On a schedule, scans recent return authorizations for spikes in a single SKU or reported defect, and alerts quality and ops in Slack when a product crosses a return-rate threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled daily run
- ActionAggregate recent RMAs by SKU and defect in PostgresPostgres
- LogicCompute return rates and flag SKUs over threshold
- LogicBuild defect summary for flagged SKUs
- OutputPost quality alert to Slack channelSlack
What it does
Turns your stream of RMAs into an early warning system for product quality problems. It periodically aggregates recent return authorizations by SKU and defect reason, compares each product's return rate against a baseline threshold, and raises an alert when one spikes — catching a bad batch before it becomes a recall.
When to use it
Use this when individual RMAs look normal but a pattern across them signals a manufacturing or supplier defect. Valuable for quality, ops, and product teams who need to spot a failing SKU within days rather than at quarterly review.
How it works
- 1A scheduled trigger runs on a regular cadence, such as every morning.
- 2The bot queries Postgres for RMA records in the recent window grouped by SKU and defect reason.
- 3A logic step computes return rate per SKU and flags any that exceed the configured threshold.
- 4If any SKU crosses the line, the bot builds a summary with counts, top defect reasons, and trend.
- 5It posts the alert to a Slack quality channel; if nothing crosses the threshold, the run ends silently.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.