DOCUMENT OPS
Sub-processor page diff to privacy review queue
Scrapes a vendor's public sub-processor page on a schedule, diffs it against the last captured snapshot.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the sub-processor check
- ActionFirecrawl scrapes and extracts the sub-processor tableFirecrawl
- ActionLoad prior snapshot and diff added/removed rowsPostgres
- LogicStop if the diff is empty
- ActionOpen a Linear privacy review issue with the diffLinear
- OutputNotify privacy owner in Slack and save new snapshotSlack
What it does
Watches a single vendor's public sub-processor list (the page they publish to satisfy GDPR transparency) and detects when sub-processors are added, removed, or relocated. Every change becomes a tracked privacy review with the diff attached, so no silent supply-chain shift slips past your DPA obligations.
When to use it
Use it for any critical vendor whose DPA requires you to be notified of sub-processor changes and gives you an objection window. Set one copy per vendor, or parameterize the URL. Ideal when the vendor only publishes changes to a web page and never emails you.
How it works
- 1A weekly schedule fires the check.
- 2Firecrawl scrapes the sub-processor page and extracts the entity table as structured rows.
- 3The flow loads the prior snapshot from Postgres and computes added/removed/changed rows.
- 4A logic step exits quietly if the diff is empty.
- 5On any change, it creates a Linear issue titled with the vendor and change count, embedding the before/after diff.
- 6It posts the same diff to the privacy Slack channel, @-mentioning the owner.
- 7The new snapshot is written back to Postgres as the next baseline.
Set it up
What you configure once, before turning it on.
- 1Connect FirecrawlCrawl, scrape, structured extract.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
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.
Gate contract signing on clause-deviation approval
When a contract is submitted for signature via webhook, diffs its clauses against approved templates and either auto-approves clean documents or holds them in Slack for explicit…
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
Log contract clause deviations to a Notion review register
On a daily schedule, scans a Drive contracts folder, diffs clauses against approved templates with OpenAI.
Weekly audit of clause drift across the contract repository
Each week, scans all executed contracts in Drive, measures how far each clause has drifted from approved templates.
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.