DOCUMENT OPS
Validate vendor price-list uploads against business rules before Postgres sync
When a vendor price-list spreadsheet is uploaded, it checks SKUs against your Postgres catalog and enforces price-sanity rules, syncs valid rows to the pricing table.
How it runs
The automated pipeline, trigger to output.
- TriggerVendor price-list uploaded to DriveGoogle Drive
- ActionLook up each SKU in Postgres catalogPostgres
- LogicApply price-sanity rules; split valid vs. rejected
- ActionUpsert valid rows into pricing tablePostgres
- OutputEmail rejection report to vendorGmail
What it does
This workflow validates a specific high-stakes document: a vendor price list. It parses the uploaded sheet, looks up each SKU against your Postgres product catalog to confirm it exists, and enforces business rules like positive prices and bounded percentage changes versus the current price. Valid rows are upserted into the pricing table; invalid rows are compiled into a report emailed back to the vendor.
When to use it
Use it when vendors send periodic price updates and a single bad row — an unknown SKU or a fat-fingered price — could push wrong pricing into your store. It enforces catalog membership and sanity bounds before anything touches the database.
How it works
- 1A new price-list spreadsheet upload triggers the run.
- 2Each row's SKU is looked up against the Postgres catalog.
- 3Price-sanity and required-field rules are applied; rows are split into valid and rejected.
- 4Valid rows are upserted into the Postgres pricing table.
- 5Rejected rows are compiled into a report and emailed to the vendor contact.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect GmailRead, draft, send, label.
- 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 Document Ops workflows
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
Flag redline deviations when a contract lands in Drive
Watches a Google Drive folder for incoming counterparty contracts, diffs each clause against your approved template library.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
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.