Hi everyone,
I wanted to ask if there is any specific advice for sharing a workflow as a JSON file. I’ve found that when the workflow is downloaded as JSON there can be quite a bit of sensitive data left in the code so I wanted to see if there are any recommendations to properly sanitise any sensitive information before sharing.
What’s the recommended approach for cleaning up a JSON workflow export before sharing it publicly and how do other people handle that?
I normally get Claude to take a look at it and tell me where I have left any identifying information (such as email address when using the Gmail node for example) and then I go through the JSON and manually replace the email address with something like “YOUR_EMAIL_ADDRESS” - this is obviously time consuming and quite prone to errors. Is there a better way to handle that?
Are there any specific fields that would be good to look out for? Other types of content that has been flagged have been things like file paths, URLs. I imagine credentials handled through n8n credentials are safe since they just have an ID. Claude always flags the instanceId, but I guess that is also safe?
Are there any built-in tools or recommended manual steps for this sanitisation process?
Any guidance on n8n’s best practices for public workflow sharing would be greatly appreciated!
Thanks in advance for your help!