Screen Vendor Bank Change Requests with Groq, DNS & Data Tables
Screen Vendor Bank Change Requests with Groq, DNS & Data Tables
Regular price
£35.99
Regular price
£35.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
Screen Vendor Bank Change Requests with Groq, DNS & Data Tables
Regular price
£35.99
Regular price
£35.99
Sale price
Unit price
/
per
Screen vendor bank change requests in minutes—using Groq, DNS (MX), and verified data tables
This n8n workflow captures vendor payment-change requests, checks them against your verified vendor bank register, validates sender-domain DNS and email tactics with Groq, and outputs a clear PASS / REVIEW / BLOCK verdict—while logging every assessment to an n8n Data Table audit trail.
What this workflow does
- Collects request details via an n8n Form trigger (sender details, email subject/body, and the claimed IBAN).
- Loads fraud thresholds and retrieves your verified vendor bank register from an n8n Data Table.
- Scores deterministic fraud signals by matching sender domain/address to the register, validating IBAN formatting/checksum, and flagging mismatches (e.g., lookalike domains, Reply-To differences, unauthorized senders, or changed bank details).
- Validates DNS credibility by querying Google DNS over HTTP to check whether the sender domain publishes MX records.
- Analyzes social-engineering pressure using a Groq chat model to produce a structured pressure score and observed tactics from the email subject/body.
- Combines signals into a final verdict (risk score → PASS / REVIEW / BLOCK) with recommended next steps.
- Audits everything by writing the full report to an n8n Data Table and showing a completion page for hold/callback verification or success.
Use cases
- Stop business email compromise (BEC) bank-detail change fraud by enforcing vendor verification before payments are updated.
- Route suspicious requests to manual review when sender identity, IBAN, or email tactics don’t match your register.
- Create an evidence-backed audit log for compliance and incident response.
Technical details
- Nodes/blocks: if, set, code, form, data table, sticky note
- External checks: Google DNS over HTTP for MX records; Groq for subject/body pressure-tactic analysis
- Outputs: structured pressure score, combined risk score, and PASS/REVIEW/BLOCK verdict with next steps
