# Export a Notebook

> Export a Notebook activity in the Databricks connector.

## Project compatibility

Windows | Cross-platform

## Overview

| Description | API Method | API Path |
| --- | --- | --- |
| Export a Databricks notebook as base64-encoded content in SOURCE, HTML, JUPYTER, DBC or R_MARKDOWN format. | GET | `/notebook_export` |

## Input

| Parameter | Description | Data Type |
| --- | --- | --- |
| Export Format | SOURCE, HTML, JUPYTER, DBC or R_MARKDOWN. Defaults to SOURCE. For example, `SOURCE`. | string |
| Databricks Notebook Path \* | Absolute path of the notebook to export, for example /Users/me/my_notebook. | string |

\* Required parameter.

## Output

| Parameter | Description | Data Type |
| --- | --- | --- |
| ID | Unique identifier of the returned record. | string |
| Content | Base64-encoded exported notebook content. | string |
| File Type | Extension of the exported file. | string |

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