The File Operations Node introduces a standardized way to manage files within AI+ Studio pipelines. It enables you to: 

• Upload static files directly into the pipeline for consistent and reusable inputs. 

• Convert existing variables such as text, URLs, Base64, or media into usable file, image, audio, or video formats. 

This functionality solves common challenges faced in AI pipeline development. For example, large text inputs often exceed token limits in Prompt Nodes, and API responses that return files cannot be used directly without conversion. By introducing native file handling, the File Operations Node eliminates these bottlenecks and ensures smooth integration across pipeline components. 

The node offers the following key benefits: 

• Streamlined workflows: File handling becomes native to pipelines. 

• Flexible input handling: Use any URL, Base64, or text-type output as a file in the Prompt Node. 

• Token optimization: Convert large text into a file to avoid token-related issues. 

Steps to Add File Operations Node 

Follow these steps to add the File Operations node to your pipeline: 

1. Open or Create a Deployment Pipeline 

• Navigate to your AI Use Case Deployment Pipeline. 

• Either open an existing pipeline or create a new one. 

2. Add the File Operations Node 

• Click the ‘+’ button on the pipeline canvas. 

• Select File Operations under Data Management. 

• The node configuration screen will appear. 

Node Configuration Options 

You can configure the node using one of the following options: 

Using Static File as File Source 

When you choose Upload Static File as the file source, the node allows you to attach a local file that will remain constant across pipeline executions. This is ideal for scenarios where you need a fixed reference file, such as sample data or predefined examples. 

Configuration Fields  

1. Element Name 

Assign a descriptive name to the node element for easy identification in the pipeline. 

Use meaningful names that reflect the file’s purpose (e.g., Customer_Training_Data). 

2. Choose File Source 

Select Upload Static File. It Indicates that the file will be uploaded from your local system rather than sourced from a variable. 

3. Upload File Section 

Once you select the file source, click the Browse button in this section. Clicking this option opens your local storage. Browse and select the file you want to upload. 

Supported Formats: Common file types such as .txt, .pdf, .csv, .doc etc. 

4. Output Variable 

Enter the name of the variable that will store the uploaded file’s output reference. This variable will be used by downstream nodes (e.g., Prompt Node). It should be unique within the pipeline. 

Behavior 

• Once the file is uploaded, the system stores it as a resource in the pipeline. 

• The Output Variable will hold the file reference, making it accessible to other nodes. 

Use Existing Variable as File Source 

The Use Existing Variable option allows you to convert the content of an existing pipeline variable into a file format. This is useful when your pipeline already generates data (such as text, URLs, or Base64) that needs to be transformed into a file for downstream nodes like Prompt Nodes. 

1. Element Name: Assign a descriptive name to the node for easy identification in the pipeline. Use meaningful names that reflect the conversion purpose (e.g., Convert_API_Response_To_File). 

2. Choose File Source: Select Use Existing Variable option. It indicates that the file will be created from the content of an existing variable rather than uploading a static file. 

3. Source Variable 

• Type: Input (Manage Resource Lookup) 

• Purpose: Select the variable whose content you want to convert into a file. 

• Details:  

  • Can be any variable type: Text, URL, Base64, or media (image, audio, video). 

  • If the variable is already a file or media type, no additional fields are required except Output Variable. 

• Behavior:  

  • For image/audio/video/file types: Output Variable Type auto-matches Source Variable Type. 

  • For text type: Requires Source Format selection. 

4. Source Format 

• It Defines how the text content in the source variable should be interpreted. 

• Available Options:  

  • Text: Treats content as plain text and converts it into a .txt file. 

  • URL: Treats content as a link pointing to a file. MIME type detection occurs at runtime. 

  • Base64: Treats content as Base64-encoded data. Requires MIME type configuration. 

Differences Between Text, URL, and Base64 Source Formats 

When configuring the File Operations Node with Use Existing Variable as File Source, the behavior and required UI fields depend on the selected Source Format. Below are the detailed explanations for each format. 

1. Text Source Format 

The source variable contains plain text data (e.g., a paragraph, JSON, or any textual content). This text will be converted into a .txt file and stored as a file resource in the pipeline. 

Configuration Fields 

• Source Format: Text 

• Output Variable: Enter the name of the variable that will store the generated file reference. The node automatically creates a .txt file from the text content. 

Key Behavior 

• No additional fields are needed. 

• Output is always a File type. 

• Ideal for reducing token usage when passing large text to a Prompt Node. 

2. URL Source Format 

The source variable contains a URL pointing to a file or media resource (e.g., an image link, audio file link). The node fetches the file from the URL during pipeline execution. 

Configuration Fields 

• Source Format: URL 

• Output Variable:  Enter the name of the variable that will store the fetched file reference. 

• Output Variable Type: Mandatory because MIME type detection occurs only at runtime. 

  • Supported Options:  

    • File: For generic files (e.g., .pdf, .txt). 

    • Image: For image files (e.g., .png, .jpg). 

    • Audio: For audio files (e.g., .mp3, .wav). 

    • Video: For video files (e.g., .mp4, .mov). 

​

Key Behavior 

• MIME type is detected dynamically during execution, so you must explicitly select the output type. 

• If the URL points to an unsupported file type, the node will fail at runtime. 

• Best for scenarios where external resources need to be integrated into the pipeline. 

3. Base64 Source Format 

The source variable contains Base64-encoded data representing a file or media resource. The node decodes the Base64 string and converts it into the appropriate file type. 

Configuration Fields 

• Source Format: Base64 

• Mime Type Resource:  

  • Purpose: Mandatory field to specify how the Base64 content should be interpreted (e.g., image/png, audio/mp3). 

  • Behavior: Can be selected from a predefined list or provided dynamically through a variable. 

• Output Variable: Enter the name of the variable that will store the decoded file reference. 

• Output Variable Type: Mandatory when MIME type is dynamic because the system cannot auto-infer the type. 

  • Options:  

    • File 

    • Image 

    • Audio 

    • Video 

Key Behavior 

• Requires explicit MIME type configuration. 

• If MIME type is static (from a predefined list), the system can auto-infer the output type. 

• If MIME type is dynamic (from a variable), you must manually select Output Variable Type. 

Summary Table

Best Practices 

• Use Text for large text inputs to avoid token limits. 

• Use URL for external resources but confirm the file type before selecting Output Variable Type. 

• Use Base64 when dealing with encoded data and always provide accurate MIME type. 

The File Operations Node is essential for use cases such as preparing large datasets for model prompts, converting API outputs into usable resources, and integrating external media files into AI workflows. By leveraging this node, users can build more robust, scalable, and efficient pipelines.