Triage and draft PII-safe support replies with OpenAI and Enterprise PII Guardrails

Description

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 formats a structured payload for CRM dispatch.

How it works
Receives an inbound support ticket via a POST webhook or a manual test run.
Normalizes the ticket fields (ID, channel, customer details, subject, and body) into a consistent payload.
Sends the ticket body to Enterprise PII Guardrails to detect and mask PII into surrogate tokens and returns a token-to-value mapping.
Sends the masked ticket text to OpenAI (gpt-4o-mini) to classify priority/category/sentiment and draft a response while preserving the surrogate tokens verbatim.
Unmasks the drafted response with Enterprise PII Guardrails using the returned mapping to restore the original customer data inside your environment.
Packages the final unmasked resolution draft and privacy metadata into a CRM-ready dispatch and audit payload.

Setup
Create an Enterprise PII Guardrails API credential (API key) and set the base URL for your deployment (demo or self-hosted).
Add an OpenAI API credential and ensure the model selection (gpt-4o-mini) is available for your account.
If using the webhook trigger, copy the webhook URL for the support-ticket-inbound endpoint and configure your ticket source to POST ticket fields (ticket_id, channel, customer_name, customer_email, ticket_subject, ticket_body).