The UnifyApps File Management operations in the Utility node create, register, retrieve, and delete files within the UnifyApps platform storage layer. Use them to persist automation outputs as platform assets, make files accessible via a time-limited public URL, or clean up temporary files when a run completes.
Overview
Six operations manage the lifecycle of files stored in UnifyApps. They let you register an existing file as a platform asset, fetch and store a remote file by URL, construct a storage path, delete a file, produce a shareable link, and upload raw base64 content directly.
_1.png&w=1920&q=75)
_1.png)
Operations
Operation | What it does |
|---|---|
Create UnifyApps asset from file | Registers an existing file as a named UnifyApps asset, making it available to other platform features. |
Create UnifyApps file from url | Fetches a file from a remote URL and saves it into UnifyApps storage. |
Create UnifyApps path for file | Constructs a storage path string for a file without uploading it — useful for building references before a write step. |
Delete UnifyApps file | Permanently removes a file from UnifyApps storage. This action cannot be undone. |
Generate public file URL | Issues a signed, time-limited URL (approximately one hour by default) for a stored file, suitable for sharing with external systems or users. |
Upload Base64 Content | Decodes base64-encoded content and uploads the resulting ile to UnifyApps storage. |
_1.png&w=1920&q=75)
_1.png)
Public URLs are time-limited: Generate public file URL produces a signed link that expires (approximately one hour by default). Do not store this URL as a permanent reference — regenerate it each time access is needed.
Notes
Keep the following in mind when using these operations.
Generate public file URL produces a signed link that expires in approximately one hour by default. Regenerate the URL each time an external system needs access rather than caching the signed link.
Delete UnifyApps file is permanent and cannot be undone from within an automation. Confirm the target path before including a delete step in a production workflow.
Create UnifyApps file from url downloads the remote file at run time. If the URL is unavailable or returns an error, the step will fail.
Upload Base64 Content expects valid base64-encoded data; malformed input will cause the step to fail.
Create UnifyApps path for file constructs a path reference only — it does not create or upload any file. Use it to pre-compute a target path before a subsequent write operation.