Monitor Vendor Sub-Processor Pages with n8n, Groq & Discord

Monitor vendor sub-processor pages for changes—automatically, with Groq and Discord

This n8n workflow keeps tabs on vendors’ public sub-processor list pages, detects when lines are added or removed, enriches new entries with Groq, and alerts you in Discord—all with a stored baseline in n8n Data Tables.

What this workflow does

• Runs on a schedule or on demand: checks all enabled vendors stored in n8n Data Tables (Monday at 08:00, or whenever you trigger it).
• Loads baseline + target URLs: for each vendor, retrieves the vendor’s sub-processor list URL and the previously seen entry register from Data Tables.
• Fetches and normalizes page content: downloads the page via HTTP, strips HTML, and builds a capped list of unique text lines.
• Flags risks and page anomalies: detects added/removed lines by comparing against the stored register, flags unreachable pages, and flags suspiciously shrunken pages.
• Country keyword tagging: tags lines that mention configured country keywords.
• Uses Groq for annotation: sends only newly added lines to Groq to extract company name and country strictly from the text, then merges annotations into the findings.
• Escalates critical findings: raises critical results when a newly added line mentions a non-approved country.
• Updates records + notifies: stores the run summary, all findings, and the updated per-vendor register back into n8n Data Tables, then posts to Discord only when the verdict is not UNCHANGED (otherwise sends a short “quiet” summary).

Use cases

• Compliance teams tracking changes to vendor sub-processors and geography.
• SaaS operators monitoring third-party updates without manually checking web pages.
• Automation engineers implementing an auditable change-monitoring pipeline in n8n.

Technical details

• Groq (Groq chat model node) for structured extraction of company name + country from newly added lines.
• Discord Webhook to send alerts (including critical non-approved country findings) or quiet summaries.
• Core workflow nodes include if, set, code, form, discord, and data table.
• Setup includes adding Groq credentials, creating a Discord webhook credential, and running the “Set Up Tables (run once)” path to create the sub_vendors and sub_r tables.