Start with a small workflow
Start with two steps: screen an invented person, then use the returned ID to fetch the evidence. Once that works, connect the steps to your customer onboarding or supplier review workflow. The SanctionsKit node can also read available sources and approved policies or retrieve a saved result.
The SanctionsKit integration is available as a verified community node on n8n Cloud and compatible self-hosted instances. It is maintained by SanctionsKit. This guide uses version 0.1.0 of n8n-nodes-sanctionskit, which was checked with n8n 2.41.4.
This optional sandbox example uses made-up records. Your first workspace also gets 250 free live screenings for its lifetime, shared by the API and dashboard. These checks do not reset each month, and no credit card is needed. Live checks use a production key and available sources. Choose a paid plan when you need more checks.
1. Install the node
On n8n Cloud, sign in as the workspace owner. Open a workflow canvas, open the node panel and search for SanctionsKit. Select the verified node, then choose Install. If it is unavailable, the workspace owner must enable verified community nodes in the Cloud Admin Panel. See n8n’s verified-node installation instructions.
On self-hosted n8n, an owner or admin can use the same verified-node search or open Settings, then Community Nodes, and choose Install. For the Settings route, enter the package and version below. Review the community-node notice, then install it. See n8n’s package installation instructions if Community Nodes is unavailable in your instance.
The SanctionsKit node package requires Node.js 22.16 or later. Your self-hosted n8n release has its own runtime requirements: n8n 2.41.4, used to check this example, requires Node.js 24 or later.
n8n-nodes-sanctionskit@0.1.02. Connect your sandbox key
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.
3. Import and run the example
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.json4. Keep retries and errors separate from results
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.
5. Connect production screening to review
For live checks, review your allowance. Create a separate production credential and choose the production option. Version 0.1.0 calls this option Production (Paid Screening), but it can also use your free lifetime live allowance. 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.
Get help with the integration
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.
Frequently asked questions
Can I install the SanctionsKit node on n8n Cloud?
Yes. It is a verified community node available on n8n Cloud and compatible self-hosted instances. The workspace owner may need to enable verified community nodes. Follow the installation steps for your instance; this guide documents node version 0.1.0 checked with n8n 2.41.4.
Does testing an n8n SanctionsKit credential run a screening?
No. The credential test reads the source catalog. Run the sample workflow to send the invented subject and fetch its evidence. Keep the API key in the credential field so it does not appear in workflow expressions or exported JSON.
Is the example’s n8n execution ID suitable for every retry?
It identifies a demo run, but a real business event needs a stable key across executions. Use an operation reference such as an onboarding event ID. Keep that key and the input unchanged when retrying the same event, including after a timeout.
What happens if I enable Continue after an n8n node error?
Route items with an error field to an error or review branch. They are unfinished checks, not no-match results. The node does not retry automatically or change coverage. Also review n8n execution-history access and retention before sending real customer inputs.
KEEP BUILDING