Triage AML Alerts in n8n: OpenSanctions, OpenAI & Jira

Instant AML Alert Triage in n8n—OpenSanctions screening, OpenAI case notes, and Jira tickets

This n8n workflow receives AML transaction alerts via webhook, screens subjects against OpenSanctions sanctions/PEP data, computes a 0–100 risk score, drafts an investigator-ready case note with OpenAI, and automatically creates a Jira Software Cloud issue—then returns the triage result as JSON.

What this workflow does

• Receives an AML alert via an HTTP POST webhook payload.
• Normalizes incoming fields (e.g., name, entity type, DOB, nationality, amount) and builds an OpenSanctions match query.
• Screens using OpenSanctions by calling https://api.opensanctions.org/match/default to find potential sanctions and PEP matches.
• Ranks matches and calculates risk (0–100) with a risk level based on match confidence, sanctions/PEP topics, and transaction attributes.
• Generates an audit-ready case note by sending the scored alert and findings to an OpenAI chat model.
• Creates a Jira issue with the case note and key risk details in your selected Jira project.
• Responds with triage output to the original webhook request, including alert ID, risk assessment, top matches, recommendation, case note text, and the created Jira issue key.

Use cases

• Automate first-pass AML investigations for SaaS compliance teams needing rapid case routing.
• Turn inbound AML alerts into consistent investigator notes and Jira tickets—reducing manual triage time.
• Provide an API-driven AML screening endpoint for internal systems that already emit alert payloads.

Technical details

• Nodes/tech stack: Webhook, HTTP Request, Code, Respond to Webhook, Jira, and OpenAI / LLM (via n8nnodes-langchainchain).
• Integrations: OpenSanctions match API, an OpenAI chat model for case-note drafting, and Jira Software Cloud for issue creation.