PCI Data retention in workflow execution history

Questions
1

i want to disable saving execution history for some projects in my deployment. there are some projects that might contain PCI data as workflow parameters in trigger, my requirement is to enforce that the execution history is not saved for these projects while i keep saving it for rest of the projects on the deployment.
i found that we can either disable the execution histories globally or at a workflow level, is there any way i can do it at a project level too? if not are there any recommended ways the community has handled the retention for such data?

i do not have control over the workflows created as this is an embedded instance however the workflows are going to be sandboxed to a project, hence the requirement to disable saving for the entire project.

Information on n8n setup

  • n8n version: 1.84.1
  • Database (default: SQLite): postgres RDS
  • n8n EXECUTIONS_PROCESS setting: main
  • Running n8n via: EKS
  • Operating system: centOS
2

Hello @Prem_Sharma

I see a way [I may be wrong], but I believe that using the CODE NODE and IF NODE in your logic can help, because you can control what will be saved and what will not.

So you could put a CODE NODE before each situation and define a JSON to take care of that desired part and then an IF NODE to direct the flow to where you want to send the files you want

It could be a faster and less costly way in your workflow.

I hope I helped in some way

If this suggestion solved your problem, mark my post as a solution (blue box with check mark) so that this ongoing discussion does not distract others who want to find out the answer to the original question and press the heart button :heart:. Thanks :+1: