Validate customer data, detect fraud, and screen sanctions — all in one n8n node (LATAM focus)

Built with n8n
1

Hey everyone !,

I built a community node for data validation, fraud detection, and compliance screening focused on Latin America: n8n-nodes-mediavox

What it does (single workflow idea):

  1. Receives a webhook with customer data (name, email, phone, address, country)
  2. Standardizes the name — detects if person vs company, separates legal suffix (SAS, SA DE CV, SpA), infers gender
  3. Validates the email — MX record check, disposable detection, typo correction (gmial->gmail)
  4. Standardizes the address — returns official location codes (DANE for Colombia, INEGI for Mexico, UBIGEO for Peru, CUT for Chile, INEC for Ecuador)
  5. Screens against sanctions lists — OFAC, UN, EU, PEP with fuzzy matching for Spanish names (handles accents, name order variations)
  6. Returns a quality score with cross-field coherence analysis (email vs name mismatch, phone prefix vs country, etc.)

Install:
Settings > Community Nodes > search n8n-nodes-mediavox > Install

Products available in the node:

  • mediaAPI:
    • DataTools — names, emails, addresses, domains, quality score
    • Security — fraud/phishing detection (SMS, WhatsApp, email), URL analysis, brand impersonation monitoring, sanctions screening (OFAC/UN/EU/PEP)
    • Recognition — document OCR, receipt extraction
    • Finance — tax ID validation (NIT, RFC, RUT, RUC), bank accounts
    • Compliance — KYC bundle (sanctions + identity + name + risk score in 1 call)
  • Turing AI — chat with RAG, content indexing, session management, feedback
  • DocumentPower — document upload, NER entity extraction, semantic search
  • Vixo ERP — clients, contracts, invoices, projects, tasks, employees

All methods load dynamically from the API — new endpoints appear automatically when added.

API Key: Free at Mediavox Developers — REST APIs for Latin America | Mediavox Developers (no credit card, 100 calls/month)

Full docs + parameter reference: n8n Integration — Mediavox Developers

Happy to answer questions or help you set it up!

2 Likes
2

The fuzzy matching for Spanish names on the sanctions screening is the standout feature here - that’s genuinely hard to get right with OFAC/UN lists because of accented characters and compound surname formats. One useful addition would be a normalization step that strips diacritics (e.g. converting “García” to “Garcia”) before the fuzzy match, so you catch entries that were entered without accents on the source lists.

3

Good point! We actually do diacritics normalization as part of the fuzzy matching pipeline — “García” matches “Garcia” and “Garciaa”. The matcher also handles compound surnames in different order (e.g. “López García” vs “García López”) and common abbreviations (Mª → María). Thanks for the feedback!