Sanctions screening in n8n

The SanctionsKit node lets you add screening to a customer onboarding or supplier review workflow. You can screen a person or organization, check available sources and approved policies, and retrieve a saved result or its evidence.

This guide uses version 0.1.0 of n8n-nodes-sanctionskit on self-hosted n8n. It is a community node maintained by SanctionsKit. n8n verification is pending, so it is not yet available as a verified node on n8n Cloud.

The free sandbox uses invented records. You can test the workflow without running a live sanctions check. Production screening requires a paid plan, a production key and the coverage you choose.

Sign in to your self-hosted n8n instance as an owner or admin. Open Settings, then Community Nodes, and choose Install. Enter the package and version below. Review the community-node notice, then install it.

The package requires Node.js 22.16 or later and was checked in n8n 2.41.4. See n8n’s installation instructions if Community Nodes is unavailable in your instance.

n8n-nodes-sanctionskit@0.1.0

Create a SanctionsKit account, then open API keys in the sandbox dashboard. Create a sandbox key with sources:read, screenings:write and results:read for this example.

In n8n, add a SanctionsKit API credential. Paste the key into its API key field and select Sandbox (Synthetic Data). Test the credential. That test reads the source catalog; it does not run a screening. Keep the key in the credential field rather than a workflow expression or exported JSON.

Copy the URL below. In a new n8n workflow, open the workflow menu, choose Import from URL and paste it. The file is tied to release 0.1.0 and contains no credentials or customer data.

Select your sandbox credential on both SanctionsKit nodes, then run the workflow manually. It screens Alex Example, an invented person, using sandbox@1. The next node uses the returned screening ID to fetch the evidence for that same result.

Open each node’s output to see the result and evidence. You can also find the screening in sandbox history. The outcome belongs to the synthetic example and says nothing about a real person.

• Run synthetic example starts the workflow manually.
• Screen fictional subject creates one screening and keeps the full response.
• Retrieve synthetic evidence returns the complete evidence document.

https://raw.githubusercontent.com/SanctionsKit/n8n-nodes-sanctionskit/v0.1.0/examples/synthetic-screening.json

The example makes an idempotency key from the n8n execution ID and item index. That works for separate demo runs. For a real workflow, use a stable business-event ID such as onboarding:customer123:v1. Keep that key and the input unchanged when retrying the same event, including after a timeout.

Errors stop the node by default. If you enable On Error, then Continue, send any item with an error field to an error or review branch. An unfinished check must never become a no-match result. The node does not retry automatically or switch to different coverage.

Check permissions for authentication errors, allowance for HTTP 402, and the original key and input for HTTP 409. Follow the error guide and idempotency guide when adding bounded retries.

When the sandbox flow works, review plans and allowances. Create a separate production credential, select Production (Paid Screening), and choose a production package or source IDs available to your workspace. Source, Get Many shows current availability; Policy, Get Page returns approved policies when your organization uses them.

Route potential matches to a person who can compare the evidence. Keep the screening ID, coverage, source versions and review decision with your business record. A no-match result applies to the selected coverage and matching rules; it is not an approval decision.

n8n can save workflow inputs and outputs in execution history. Set access and retention for your instance before sending real customer details. Get Evidence returns the full evidence document, while minimal retention leaves out submitted inputs and limits later replay. The evidence guide explains what is retained.

The package README covers every operation and output option. Report an integration issue or contact SanctionsKit if you get stuck. Include the node version, operation and error code, with API keys and customer details removed.