# Upload a File

> Upload a File activity in the Databricks connector.

## Project compatibility

Windows | Cross-platform

## Overview

| Description | API Method | API Path |
| --- | --- | --- |
| Write a file to a Databricks Unity Catalog volume. Requires catalog, schema, volume and file_name; text is sent as-is, binary must be base64-encoded by the caller. | PUT | `/fs/files/{catalog}/{schema}/{volume}/{file_name}` |

## Input

| Parameter | Description | Data Type |
| --- | --- | --- |
| Volume \* | Name of the Unity Catalog volume. For example, `my_volume`. | string |
| Schema \* | Name of the schema that contains the volume. For example, `default`. | string |
| Catalog \* | Name of the Unity Catalog catalog that contains the volume. For example, `workspace`. | string |
| File Name \* | Path of the file inside the volume, relative to the volume root. For example, `reports/orders.csv`. | string |
| File Contents \* | Raw file contents to write. Text is sent as-is; binary payloads must be base64-encoded by the caller. For example, `order_id,total`. | string |
| Overwrite | Replace the file if it already exists. Default: `true`. | boolean |

\* Required parameter.

## Output

The connector does not define named output parameters for this activity. To see what Databricks returns in your workspace, select **Refresh Schema** in the activity and inspect the output schema.

:::note
You might see variations in the output depending on where you run the activity. In API workflows and Maestro Flow, a single response object containing all the fields is returned. In RPA workflows, not all fields are exposed, but you can still retrieve them from the exposed response object.
:::