Skip to main content
Use this when you are about to write a file and want to avoid overwriting something that is already there. It takes the destination path you give it, checks the chosen filesystem connection, and if a file already exists at that path it applies the conflict resolution strategy you pick to produce a free path instead. For example, exports/orders.json becomes exports/orders-1.json when the original is taken. When the path is already free, it is returned unchanged. The path it returns is meant to be passed on to a step that writes, copies, or moves the file, so the same conflict handling is also available directly on the Filesystem write, copy, and move transformers.

​
Fields

​
Sample data

This feature does not transform a value on its own. It looks at the live filesystem to decide whether a path is already in use, then hands back a safe path, so there is no fixed before/after to show: the same input can return a different result depending on what files already exist. Below is a typical configuration and how it behaves.
FieldValue
Filesystem connectionA connection where exports/orders.json already exists
When the file existsAdd an increasing number to the filename (default pattern, starting at 0)
With this configuration, feeding in the path exports/orders.json returns exports/orders-1.json, because the original name is already taken. If exports/orders.json does not exist yet, the same path is returned untouched.