Assess GDPR breach risk and 72-hour deadlines with Groq and data tables
Ready for 3.0What this workflow does
This AI workflow has 32 nodes and runs manually, when you click “Execute workflow” (plus 2 other triggers). Along the way it connects Groq Chat Model and Discord.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 2 other triggers).
- Create Risk Factor Table (Data table): create (table)
- Set Breach Policy (Edit Fields (Set)): sets 4 fields: deadline_hours, high_risk_threshold, large_number_threshold…
- Set Reminder Policy (Edit Fields (Set)): sets 1 field: warn_hours_left
- Create Register Table (Data table): create (table)
- Load Risk Factors (Data table): get
- Read The Register (Data table): get
- Create Findings Table (Data table): create (table)
- Score The Breach (Code): runs custom JavaScript code
- Check The Deadlines (Code): runs custom JavaScript code
- Create Reminder Table (Data table): create (table)
…plus 17 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (12)
- Manual Trigger
n8n-nodes-base.manualTrigger - Data table
n8n-nodes-base.dataTable - Code
n8n-nodes-base.code - n8n Form Trigger
n8n-nodes-base.formTrigger - Edit Fields (Set)
n8n-nodes-base.set - Basic LLM Chain
@n8n/n8n-nodes-langchain.chainLlm - Groq Chat Model
@n8n/n8n-nodes-langchain.lmChatGroq - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - If
n8n-nodes-base.if - Discord
n8n-nodes-base.discord - n8n Form
n8n-nodes-base.form - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Quick overview This workflow collects suspected personal data breach reports via an n8n form, scores them against GDPR risk factors stored in n8n Data Tables, uses Groq to validate additional risk factors from the text, calculates the 72-hour notification…