Review pinned data before sharing an n8n workflow
Find pinned node data in exported n8n workflows and separate useful test fixtures from information that should not travel.
Treat test fixtures as real data
Pinned examples can make a workflow easier to understand, but samples may contain customer records, messages or internal identifiers. A workflow file is not automatically suitable for public sharing just because the credentials themselves are managed elsewhere.
Inspect the pinData object
Flowprep counts non-empty pinned node arrays in the top-level pinData object and raises a review finding. It does not display the pinned values in the handoff report. This identifies a common place to inspect; it does not mean that other fields contain no private information.
Choose a minimal reproduction
For a public example, create a small synthetic input that demonstrates the behavior you need. Keep the same field shape, include one useful edge case and document the expected output. Avoid copying a large production payload merely because it was convenient during development.
Check the final artifact
Make deliberate changes in n8n or your own editor, then export again. Flowprep does not remove or rewrite pinned data automatically. Inspect the actual file you intend to send and run the destination workflow with the agreed test payload.
Flowprep keeps the analysis local and the original JSON unchanged.
Open workflow checker →