GDPR Access & Erasure Evidence Logging with Groq + Data Tables

Prove GDPR Actions with Automated Access/Erasure Evidence Logging (Groq + Data Tables)

This n8n workflow receives a GDPR request (Access or Erasure), searches multiple connected systems stored in n8n Data Tables, logs per-system evidence, calculates a compliance verdict with a 30-day deadline, and produces a Groq-written plain-English summary—without letting the summary override the code-decided outcome.

What this workflow does

• Accepts a GDPR request via another workflow input or a built-in form with an email identifier and request type (Access or Erasure).
• Applies policy guardrails by enforcing a minimum identifier length; if the identifier is too short to safely match, the workflow refuses to search.
• Searches multiple systems (three demo systems backed by n8n Data Tables by default: CRM contacts, support tickets, and a mailing list), continuing even if one system errors.
• Records evidence per system by writing a row per system into an n8n Data Table, capturing whether each system answered, failed, or was not searched.
• Calculates a GDPR case verdict (DATA_FOUND, NO_DATA_FOUND, INCOMPLETE, or NOT_SEARCHED) and sets a response due date using a 30-day window.
• Generates a constrained summary with Groq, producing a one-paragraph plain-English explanation that cannot override the workflow’s verdict.
• Creates a case register entry in a register Data Table using a hash of the identifier, then returns case details to the calling workflow or shows a result page for form submissions.

Use cases

• GDPR Access requests: verify which CRM, support, and mailing list records exist for a subject.
• GDPR Erasure requests: document what data systems were searched and the status of each.
• Compliance operations: maintain an auditable case register with deadlines and system-level evidence.

Technical details

• Groq: Groq API credential + Groq Chat Model node for the one-paragraph summary.
• n8n Data Tables: demo searches for CRM contacts, support tickets, and a mailing list; plus an evidence table and a case register table.
• Core nodes: if, set, code, form, data table, sticky note.