OFAC SDN Name Screening n8n Workflow w/ Webhook & Discord Alerts

Screen names against OFAC SDN lists with an n8n webhook—and get Discord alerts for possible matches

This OFAC SDN Name Screening n8n Workflow lets you submit a name to a header-authenticated webhook, automatically compares it to the latest OFAC SDN list and aliases, logs outcomes in n8n Data Tables, and posts Discord alerts when a result is a POSSIBLE MATCH (or UNAVAILABLE).

What this workflow does

• Receives screening requests: a POST to the Webhook endpoint with header authentication and a JSON body containing the name to screen.
• Fetches the latest OFAC data: downloads the primary OFAC SDN CSV and the alternate names (alias) CSV via HTTP.
• Loads human-cleared pairs: reads current “cleared” name pairs from n8n Data Tables to suppress matches that were previously reviewed as cleared for the exact query/matched-name pair.
• Normalizes and compares deterministically: normalizes the input name and compares it against every OFAC primary and alias entry. If either list cannot be read, it returns UNAVAILABLE (503).
• Applies a match threshold: builds a candidate match list while honoring the suppression rules for cleared pairs.
• Notifies and logs: posts a Discord message for POSSIBLE MATCH results (and for UNAVAILABLE), then writes the screening outcome to a log table.
• Responds with a verdict: returns JSON verdict, match details, and a screening disclaimer to the webhook caller.
• Weekly audit summary: runs every Monday morning to summarize the past week’s screenings from the log and posts the audit summary to Discord.

Use cases

• Sanctions screening for onboarding/KYC flows that need an API-style OFAC SDN check.
• Automated monitoring that alerts compliance teams in Discord for review-worthy matches.
• Operational visibility via a weekly audit summary built from logged screening outcomes.

Technical details

• Webhook + Header Auth for secured POST requests
• HTTP downloads of OFAC SDN CSV and alias CSV
• n8n Data Tables: sanctions_screenings and sanctions_cleared (via the manual “Set Up Tables” path)
• Nodes used: if, set, code, discord, webhook, data table

Note: This workflow provides screening results and alerts for review; it includes a disclaimer in the webhook response.