The Files by UnifyApps node provides a set of file-handling actions for an automation, plus a trigger that fires on new or updated files. The walkthrough below focuses on the Upload file action, which creates a file object that other nodes in the automation can consume as a data pill.
Overview
Files by UnifyApps covers the common file operations an automation needs: creating a file, uploading a file from a URL or base64 content, retrieving or copying an existing file, deleting a file, appending lines to a file, generating a PDF, and detecting a file's MIME type — plus a trigger that fires when a file is created or updated. Each action returns (or the trigger provides) a file object that other nodes in the automation can consume as a data pill, so files can be passed through automations and into other applications as needed.


Use Case
A practical scenario involves taking a public PDF URL and uploading it to Amazon S3. The URL is passed into Files by UnifyApps, enabling creation of a file object from it, which is then passed into the Amazon S3 node for upload. To generate a file within the automation, such as a PDF, use the Create a file or Create a PDF file action listed below.
How to Use Files by UnifyApps
Add the Files by UnifyApps node and select "Upload file" as the action.
Fill in the input parameters:
Option — Choose URL or Base64 Content.
URL / Base64 Content — Provide the corresponding data.
File Name — Optional. Enter your file name (for example, myFile.txt). If left blank, a random UUID is used as the file name.
Mime Type — Optional. Specify the file format (text/csv, image/png, audio/mp3, etc.). If left blank, the file is uploaded as a generic
application/octet-streamtype, which can break downstream nodes that branch on MIME type.Upload to public bucket — Optional, off by default. Turn on to store the file in a separate public bucket instead of the automation's private storage; files there don't need a signed URL to be read, so anyone with the URL can access them.
Validate File — Optional, off by default. Turn on to check the file against your workspace's file validation settings (allowed MIME types, antivirus scanning, and similar checks, set by your workspace admin, not from this node). If the file fails validation, the action fails with an error.
The output returns a fileDetails object with File Type, Mime Type, Name, Size, Source, and Source Type. Use this fileDetails object to pass the file to downstream nodes.
Other actions and the trigger
Files by UnifyApps also includes the following actions and a trigger.
Action / trigger | What it does |
|---|---|
Create a file | Creates a file in the file system. |
Create a PDF file | Creates a PDF file. |
Get File | Gets file details from a file path. |
Get File Mime Type | Gets the MIME type of a file. |
Copy file | Copies a source file's content to a target file. |
Delete File | Deletes a file from the file system. |
Append line(s) to file | Appends one or more lines to a file. |
Triggers on new or updated file | Fires when a file is created or updated. |
Notes
The Files by UnifyApps node works best when you follow these practices:
Pass the fileDetails object from the output to downstream nodes — this is the standard file pill format accepted by app connectors.
Set the MIME type explicitly when you know the file format rather than relying on detection — this prevents misidentification when the file content is ambiguous.
Use the URL option when the file is publicly reachable; use Base64 Content when the file has already been downloaded or generated earlier in the automation.
Name files with their correct extension — downstream nodes that branch on file type use the extension and MIME type together to determine routing.