# Create a Directory

> Create a Directory activity in the Databricks connector.

## Project compatibility

Windows | Cross-platform

## Overview

| Description | API Method | API Path |
| --- | --- | --- |
| Create a Directory on a Databricks Unity Catalog volume. Parent directories are created as needed and the call succeeds if the directory already exists. | PUT | `/fs/directories/{catalog}/{schema}/{volume}/{directory_name}` |

## Input

| Parameter | Description | Data Type |
| --- | --- | --- |
| Directory Name \* | Path of the directory inside the volume, relative to the volume root. For example, `reports/2026`. | string |
| 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 |

\* 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.
:::