Triage and draft PII-safe support replies with OpenAI and Enterprise PII Guardrails
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 7 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects OpenAI and Piiguardrails (community).
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Prepare Ticket Data (Edit Fields (Set)): sets 6 fields: ticket_id, channel, customer_name…
- Mask PII Data (Pii Guardrails): uses Pii Guardrails
- OpenAI: uses OpenAI
- Restore PII Data (Pii Guardrails): unmask
- Build CRM Dispatch Data (Edit Fields (Set)): sets 7 fields: ticket_id, customer_name, customer_email…
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-piiguardrails is verified or supports 3.0 (used in Mask PII Data, Restore PII Data).
Nodes used (5)
- Manual Trigger
n8n-nodes-base.manualTrigger - Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - Pii Guardrails
n8n-nodes-piiguardrails.piiGuardrails - OpenAI
@n8n/n8n-nodes-langchain.openAi
From the author
Quick overview This workflow ingests customer support tickets via webhook or manual trigger, masks sensitive PII with Enterprise PII Guardrails, uses OpenAI (gpt-4o-mini) to triage and draft a reply using surrogate tokens, then restores the original PII and…