Anonymize PII in Webhook Payloads with External Detection

Anonymize PII in Webhook Payloads with External Detection—before data leaves your system

This n8n workflow accepts incoming POST requests, detects likely personally identifiable information (PII) using an external HTTP detection API, anonymizes high-risk fields, forwards the cleaned payload to a downstream endpoint, and returns an audit summary to the webhook caller.

What this workflow does

• Receives a POST request via an n8n webhook (default webhook path: /pii-anonymize).
• Validates the request, generates a request ID, and extracts likely PII candidate fields, including one-level nested fields.
• Calls an external PII detection HTTP endpoint with the extracted candidate fields after a brief wait.
• Interprets the detection response and also uses fallback regex heuristics to assign a `PII type` and `risk score` per field.
• Anonymizes fields above the risk threshold by applying type-aware transformations such as hashing, masking, or redacting.
• Forwards the anonymized payload (along with a change count) to a downstream HTTP endpoint for logging or further processing.
• Builds an audit record and returns a JSON response containing the anonymized data, audit summary, and an HTTP status indicating success or detection failure.

Use cases

• SaaS operators needing to reduce PII exposure when integrating webhook-based data ingestion.
• Automation engineers protecting customer data before sending it to analytics, ticketing, or internal logging endpoints.
• Compliance-focused teams that require an audit trail whenever sensitive fields are anonymized.

Technical details

• n8n nodes: Code, Wait, Webhook, Sticky Note, HTTP Request, Respond to Webhook.
• External integrations: configurable PII detection API (replace placeholder URLs) and a downstream audit/logging endpoint (placeholder currently: https://httpbin.org/post).
• Behavior: external detection + regex fallback, then risk-threshold anonymization.

Tip: If your detection or downstream endpoints require authentication, add the required headers/credentials in the HTTP Request nodes.