By Greg Nowak. Updated 9 November 2026.
A green tick in n8n tells you the workflow finished. It does not tell you where the customer’s message is now, who can read it, or when the last copy will disappear.
For a business owner approving an AI pilot, those are handover questions. Before increasing volume, ask the team to demonstrate what happens to one enquiry across n8n, OpenAI and the CRM.
Follow one enquiry, including the failure path
Consider a simple example: a form collects a name, email address, customer reference and message. n8n sends text to OpenAI for classification, then writes a category and summary into the CRM. This is an illustrative design, not a client case.
Start by reducing what leaves each step. Does classification need the customer reference, or can n8n attach it afterwards? Check free text too: removing an email field achieves little if the message contains the same address. Inspect the generated summary for personal details before saving it.
Then follow a controlled failure. Does an error alert copy the message into email, a support ticket or a logging service? Add confirmed destinations to the map, including any agency account used during development.
Put the retained copies and their owners on one page
Complete this table using actual settings and permissions. For each row, record a retention period, deletion method and named owner. “The supplier handles it” needs supporting evidence.
| Destination | What to inspect | Decision to record |
|---|---|---|
| Form or inbox | Original fields, message and attachments | Who needs the original, and until when? |
| n8n | Saved inputs, outputs, errors and binary files | What is saved, who can reveal it, and what does pruning exclude? |
| OpenAI API | Endpoint, request settings, uploaded objects and tools | Which retention controls and exceptions apply? |
| CRM | Summary, category and linked customer record | When should the output be removed? |
| Logs, exports and backups | Additional copies confirmed with system owners | Who controls access, expiry and removal? |
The EDPB’s small-business guidance connects data minimisation with retention periods defined by purpose and a deletion procedure. Apply that separately to the original enquiry, troubleshooting records and CRM output. They need not share the same expiry date.
n8n redaction hides payloads; storage needs a separate decision
n8n’s execution redaction is available on Enterprise Cloud and Enterprise self-hosted plans. It hides payloads when executions are viewed while retaining status and timing. It does not change or encrypt database contents, or restrict data sent downstream.
Check both manual and production controls. Current documentation also covers instance-wide enforcement from n8n 2.26.0. That policy does not travel with workflows through source control, so verify the destination instance during deployment.
Review who has execution:reveal permission and who can access the database directly. Reveal access has exceptions, including executions using dynamic credentials. Code node console.log output falls outside redaction; inspect any customer content written there.
Ask the person responsible to demonstrate ordinary viewing, privileged access and retention separately. A hidden payload proves only the first control.
Choose what n8n saves, then verify pruning
n8n’s execution-data controls cover successful, failed and manual runs, plus execution progress. Check instance configuration alongside individual workflow settings.
For self-hosted deployments, useful settings to review include EXECUTIONS_DATA_SAVE_ON_SUCCESS=none, EXECUTIONS_DATA_SAVE_MANUAL_EXECUTIONS=false and EXECUTIONS_DATA_SAVE_ON_PROGRESS=false. Decide separately whether failed runs need their payloads retained for troubleshooting.
Pruning is enabled by default. Its documented thresholds are 336 hours, or 14 days, and 10,000 executions; either can trigger pruning. Removal happens in stages with a safety buffer, so the age threshold is not an exact deletion deadline.
New, running and waiting executions are ineligible. Annotated executions, including tagged or rated ones, are never pruned. Binary pruning covers the active storage mode; check previous storage locations after a change.
Have the operator show the deployed values and handle exceptions explicitly. Keep enough diagnostic information to answer support questions, with an agreed expiry for any customer payloads retained.
Check the OpenAI request, not just the integration name
OpenAI’s official data-controls documentation distinguishes abuse-monitoring logs from application state. API content is not used for model training unless you opt in. That does not mean it is immediately deleted.
Default abuse-monitoring logs may contain prompts and responses and remain for up to 30 days, with legal and harm-prevention exceptions. Separately, the Responses API documents a default 30-day application-state retention period; stored responses remain for at least 30 days, subject to exceptions.
Where appropriate, explicitly set store: false to disable response storage. This does not disable default abuse monitoring or enable Zero Data Retention. Zero Data Retention and Modified Abuse Monitoring require approval and have endpoint and feature limitations.
Record the endpoint, model, request parameters, tools and effective project controls. Uploaded files, persistent objects, caching and external tools need their own checks against the relevant documentation entries.
Test deletion before expanding the pilot
Create a synthetic enquiry with a distinctive marker. Run successful, failed and manual executions; include an annotated execution to check the pruning exception. Search every confirmed destination for the marker, then apply the planned deletion or expiry actions.
Inspect again after the relevant schedules and buffers. Record what disappeared, what remains, why and who must act. Ask the hosting owner how backups expire and how restored data is handled.
You may be unable to inspect provider-managed retention directly. Distinguish observed deletion from conclusions based on documented policy and account settings.
If your team needs help closing these gaps, I can review one workflow with the business owner and implementer. We can scope the work around a retention map, access review, configuration changes and a deletion-test record. Get in touch with Greg with the workflow’s purpose and systems involved, and we can agree a useful starting point.
Related on GrN.dk
- When AI writes JSON, one bad field can break the workflow
- From Supplier PDFs to Product Data: Where AI Needs a Second Check
- When the AI API Says “Try Again,” What Does Your Customer See?
Need help with this kind of work?
Discuss a workflow data audit with Greg Get in touch with Greg.