u/Which_Effective9604

▲ 9 r/n8n

How are people checking AI-generated Slack/Gmail messages before sending in n8n?

Spent some time testing a small n8n setup where an AI agent drafts a Slack message from internal HR-style data.

Technically, the flow worked.

But the uncomfortable part was that the AI could easily produce sensitive details before anything checked the output.

Things like:

employee names
emails and phone numbers
salary or HR notes
confidential review details

It made me wonder how people are actually handling this in real n8n workflows.

Are most builders adding approval steps before AI-generated messages go to Slack, Gmail, or a CRM?

Or are people letting the AI output send directly and just trusting the prompt?

Curious what technical pattern people usually use here: approval step, validation node, human-in-the-loop, or something else?

reddit.com

u/Which_Effective9604 — 24 hours ago

▲ 2 r/n8n

How I stopped my AI support agent from leaking customer PII

I was building a basic support automation and noticed the AI was including the customer's full name, email, and phone number in the reply. Just casually. Ready to send.

Added an HTTP Request node that checks the outbound message before it goes anywhere. It returns a verdict and a cleaned version of the payload if PII is detected. The workflow then sends the masked version instead of the original.

Workflow here: https://github.com/Horace-Jacob/n8n-workflows-breakpoint

Nodes used: Google Sheets, AI Agent, HTTP Request, IF node to branch on verdict.

Happy to answer questions if you want to adapt it for a different use case.

u/Which_Effective9604 — 3 days ago