The Files by UnifyApps node provides a set of file-handling actions for an automation — including uploading a file from a URL or base64 content, retrieving, copying, deleting, and appending to files, generating PDF files, and detecting a file's MIME type — 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: 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.

How to Use Files by UnifyApps

1. Add the Files by UnifyApps node and select "Upload file" as the action.

2. Fill in the input parameters:

   • Option — Choose URL or Base64 Content

   • File Name — Input your file name

   • MIME Type — Specify the file format (text/csv, image/png, audio/mp3, etc.)

   • URL / Base64 Content — Provide the corresponding data

3. 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.

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.

A well-configured Files by UnifyApps node reduces errors and keeps automations maintainable.