n8n Easycompliance Sanctions & PEP List Check Workflow

Instantly check sanctions and PEP risk with an n8n Easycompliance name-screening workflow

This n8n Easycompliance Sanctions & PEP List Check workflow lets you manually screen a person’s name against easycompliance lists, then automatically routes the result to the right path—handling hits (matches) or continuing when there’s no hit.

What this workflow does

• Manual execution: The workflow starts when you manually run it in n8n.
• Sanctions check example: It sends the name “Abu Brays” to easycompliance to perform a sanctions list check.
• Evaluate response: It checks the easycompliance response to determine whether a sanctions hit is returned.
• Branching logic: Matches are routed to a “handle hit” path (e.g., notifying your compliance team), while non-matches go to a “no hit” path to continue processing.
• PEP screening with the same flow: You can switch the List parameter from Sanctions to PEP to screen for politically exposed persons.

Use cases

• Compliance triage: Quickly review suspected matches by sending alerts on “hit” cases.
• Customer onboarding screening: Block or escalate onboarding when a name matches a sanctions/PEP list; proceed automatically for no hits.
• Operational demos & testing: Use the provided example flow as a baseline for your own compliance automation in n8n.

Technical details

• n8n workflow category: n8n automation workflow (demo workflow)
• Nodes/logic mentioned: manual trigger, if branching, no op, sticky note
• Integration: n8n-nodes-easycompliance (community node) via an easycompliance API credential

Requirements: An easycompliance account with API access (API key + API URLs from easycompliance customer service) and the n8n-nodes-easycompliance community node installed (Settings → Community Nodes).