DATA OPS
Replay Quarantined Reject Rows from S3 into Salesforce
Scans an S3 quarantine bucket of previously rejected reverse-ETL rows, retries each against Salesforce.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled replay sweep every few hours
- ActionList pending reject files in S3 quarantine prefixAWS S3
- ActionRetry upsert of each row to SalesforceSalesforce
- LogicBranch success vs still-failing and check attempt cap
- ActionArchive successes and rewrite failures with attempt count in S3AWS S3
- OutputPost max-attempt rows to Slack for manual reviewSlack
What it does
Failed reverse-ETL rows often get dumped as JSON files into an S3 reject bucket and forgotten. This workflow drains that backlog: it reads each quarantined file, retries the write to Salesforce, archives the ones that now succeed, and keeps the rest with an updated attempt counter so they don't loop forever.
When to use it
Run this on a schedule after your team fixes data-quality issues upstream (deduped accounts, corrected picklist values). It clears the reject backlog without anyone hand-replaying files, and it surfaces rows that have exhausted their retries.
How it works
- 1A schedule triggers the replay sweep, e.g. every few hours.
- 2The flow lists pending reject files under the S3 quarantine prefix.
- 3For each row it attempts an upsert to the matching Salesforce object.
- 4A branch separates rows that now succeed from rows that still fail.
- 5Successful rows are moved to an archive prefix and removed from the quarantine prefix.
- 6Still-failing rows are rewritten with an incremented attempt count; those past the max-attempt limit are posted to a Slack channel for manual review.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 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.