> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# File output tabular format extension overview

The file output tabular format extension exports data from [steps in an agreement process](https://support.docusign.com/s/document-item?bundleId=yff1696971835267\&topicId=afu1730332596907.html) to tabular format files stored in cloud storage systems. Supported file types are Excel sheets, Google sheets, and CSV files.

## Use a file output tabular format extension in a workflow

After a file output to tabular format extension app has been [installed and connected](https://support.docusign.com/s/document-item?bundleId=ous1698169987748\&topicId=ctg1698170340729.html) to a Docusign account, a workflow process builder can include a step that invokes the extension. In the example described here, a process builder defines a workflow that verifies an employee’s right to work in compliance with the [United Kingdom’s Right to Work laws](https://www.docusign.com/en-gb/blog/digitalise-your-right-to-work-process-with-digital-identity-checks). The workflow steps include:

1. An employee supplies their information including a Share Code in a web form and submits it.
2. The employee completes identity verification.
3. The extension writes the values entered by the employee and the result of their identity verification to a spreadsheet for compliance.

Expand the sections below to see how a file output tabular format extension functions during workflow [configuration](https://support.docusign.com/s/document-item?bundleId=yff1696971835267\&topicId=tco1697826811758.html) and [execution](https://support.docusign.com/s/document-item?bundleId=yff1696971835267\&topicId=zbf1698707257742.html). See [File output tabular format actions and capabilities](/extension-apps/extension-apps-101/supported-extensions/file-output-tabular-format#file-output-tabular-format-actions-and-capabilities) for details about the functionality.

#### Workflow configuration: The process builder selects the extension

When adding a workflow step to export data to tabular format, the process builder selects the extension that has been installed to their Docusign account.

![A screenshot of the menu when adding a file output tabular format step to a workflow](/_fern-files/_img/f8677a777cae1040d7a23d7c3367835114bc2402ca964e560535b3846e47df37.webp)

#### Workflow configuration: The process builder selects a drive

The process builder configures the file output step. During step configuration, the file output tabular format extension can be invoked to list the drives in the cloud storage system. This enables the process builder to select the destination drive where the data will be written.

Drive selection is an optional [capability](/extension-apps/extension-apps-101/concepts/capabilities) for file output to tabular format. If the extension does not implement this feature, process builders will not be able to select a drive.

**Note:** If the cloud storage system does not have the concept of drives and instead organizes folders and files under a different container type, the extension can retrieve a list of those containers instead. They will appear in the step configuration pageʼs **Select Drive** list.

![A screenshot of the process of selecting a drive in a file output tabular format configuration](/_fern-files/_img/d37320a12a2eb5fa9f6557ec7aa4d7ce5535f3a2b8909a963163f49cf56fa604.webp)

#### Workflow configuration: The process builder selects a file

Another configuration option is the ability to select a destination file in the cloud storage system. The file output tabular format extension can be invoked to display a list of files in a drive or directory.

File selection is an optional capability for file output to tabular format. If the extension does not implement this feature, process builders will not be able to select a file.

![A screenshot of the process of selecting files while configuring a file output tabular format step](/_fern-files/_img/524b4ae216244f3e91853245a93c6815a8de1e5873df8d21c1051160f10d26c3.webp)

#### Workflow configuration: The process builder selects the variables to be exported

The process builder’s last configuration step is to select the variables whose values are to be exported. When writing values to an empty spreadsheet, each variable selected will be assigned a column and each column will be given a generic heading like **Column 1** that can be edited directly in the destination sheet. Whenever an instance of the workflow is run, a new row will be added to the spreadsheet containing the values of that instance’s selected variables.

When writing values to a spreadsheet with existing data, the values of each instance’s variables will be written to a new row under the spreadsheet’s existing columns.

![A screenshot of the process of selecting variables to export in a file output configuration step](/_fern-files/_img/da79f9d7ec44c0e76aab5ededd42a78bda37d8ddcc70f5136fd247ebc48c3091.webp)

#### Workflow execution: The employee completes a web form

When the example workflow is executed, the employee’s first step is the completion of a web form. The employee enters information in the form fields and submits the form.

![A screenshot of a web form collecting employee information](/_fern-files/_img/390b8a1fe0c6512cdb4aa9df058ddfd7e32c60f5c28fed6a847c3b0e87a76b5d.webp)

#### Workflow execution: The employee completes identity verification

The employee completes the identity verification step by uploading a photo of their ID document.

![A screenshot of the identity verification options provided by Docusign](/_fern-files/_img/de4e2cade33917f73dc436b517a733a003e3828ebc6a37ae8bdabb73fda7e31b.webp)

#### Workflow execution: The fields are exported to the tabular format file

After the employee has completed the identity verification step, the workflow reaches the file output step and writes the values of the selected variables to the file that the process builder selected. The values will be written to a new row in the sheet.

![A screenshot of a .csv file with data exported to it from a workflow](/_fern-files/_img/82bfc0cf53ce3d9329cecbb5f37cbefa7e2cd023b8ba45de6f5acd4897646374.webp)

## File output tabular format actions and capabilities

A file output tabular format extension implements the [actions](/extension-apps/extension-apps-101/concepts/actions) and [capabilities](/extension-apps/extension-apps-101/concepts/capabilities) listed below. Both actions and capabilities send requests to an external API service. Actions are required and provide the core functionality for an extension. Capabilities are optional and offer additional features to enhance the core functionality.

| Action or capability                                                                                                                                 | Executed when                                                                                                                                                                                                                                                         | Description                                                                                                                                                                                                                                                                                                                                                                                                            |
| ---------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Export to Destination](/extension-apps/extension-app-reference/extension-contracts/file-output-tabular-format#export-to-destination) action         | A running workflow instance reaches a file output step that exports values of workflow variables to a spreadsheet.                                                                                                                                                    | **Required.** Exports values of workflow variables to a spreadsheet. If the file output tabular format extension implements **List Drives**, the values are written to a file in the drive (or similar container type) that the process builder selected during workflow configuration. If the extension implements **List Directory Contents**, the values are written to the file that the process builder selected. |
| [List Headers](/extension-apps/extension-app-reference/extension-contracts/file-output-tabular-format#list-headers) action                           | While configuring a file output to tabular format workflow step, a process builder selects variables whose values are to be exported.                                                                                                                                 | **Required.** To ensure no data corruption, a request is sent to check that the number of columns in the destination sheet is greater than or equal to the number of variables being exported. If this check is not successful, the process builder will not be able to complete the step configuration.                                                                                                               |
| [List Directory Contents](/extension-apps/extension-app-reference/extension-contracts/file-output-tabular-format#list-directory-contents) capability | While configuring a file output to tabular format workflow step, after selecting a drive, a process builder selects a [connection](/extension-apps/extension-apps-101/concepts/connections).                                                                          | **Optional.** Gets a list of the folders and tabular format files in the selected drive (or similar container type) or directory on the cloud storage system. This enables the process builder to select a destination file from a list of existing files.                                                                                                                                                             |
| [List Drives](/extension-apps/extension-app-reference/extension-contracts/file-output-tabular-format#list-drives) capability                         | While configuring a file output to tabular format workflow step, a process builder selects a [connection](/extension-apps/extension-apps-101/concepts/connections). If only one connection is available, this request is sent when the step configuration page loads. | **Optional.** Gets a list of drives on the cloud storage system. This enables the process builder to select a destination drive. This capability is appropriate for cloud storage systems that have drives or similar structures that contain folders and files.                                                                                                                                                       |

## Workflow configuration requests to the external system

This flow shows how the file output tabular format extension’s [actions](/extension-apps/extension-apps-101/concepts/actions) and optional [capabilities](/extension-apps/extension-apps-101/concepts/capabilities) can be invoked during configuration of a Maestro workflow. The process builder is able to select a drive and file destination where the workflow variable values will be written.

> **Note**
>
> This flow describes the sequence of calls to the external system when an extension app implements the optional **List Drives** and **List Directory Contents** capabilities. An extension app that exports values to tabular format can be implemented without these capabilities. See [External system logic to return file destination options](/extension-apps/extension-apps-101/supported-extensions/file-output-tabular-format#extension-implementation-details) for details.

**List Drives capability:** When a process builder configures a file output step, Docusign sends a **List Drives** request to the external system to retrieve a list of drives or similar structures that contain folders and files. The file output step configuration page displays the list in a dropdown.

**List Directory Contents capability:** When a drive has been selected, the system launches a **List Directory Contents** request. The page displays the file names from the response in a list. The process builder selects the destination file to which the values will be exported.

**List Headers action:** After the process builder selects the variables to be written to the destination file, the system sends a **List Headers** request to compare the columns in the destination file to the number of variables being exported. This prevents data corruption in the destination file.

![A diagram of the file output tabular format extension workflow configuration requests](/_fern-files/_img/2468cffacca0c88051cac9bb4f7be6d4c6b901899c791568f63c2c4cd068a843.webp)

## Workflow instance runtime requests to the external system

This flow shows how the file output tabular format extension is invoked during the execution of a workflow instance.

**Export to Destination action**: When a running workflow instance reaches a file output to tabular format step, Docusign sends an **Export to Destination** request to the external system. The request includes a Base64-encoded string representing the drive and file information, an array of strings representing the column header names, and a two-dimensional array of strings representing the data being written to the file.

![A diagram of the requests in a file output tabular format extension at runtime](/_fern-files/_img/3f3a8d845e2006cc4a1dbe9941348b20eb3ce4127d0739e84c0e2a8e4e988af4.webp)

## Plan a file output to tabular format implementation

These sections describe options that should be considered when planning a file output to tabular format implementation:

* [Extension implementation details](/extension-apps/extension-apps-101/supported-extensions/file-output-tabular-format#extension-implementation-details)
* [Workflow configuration options and restrictions](/extension-apps/extension-apps-101/supported-extensions/file-output-tabular-format#workflow-configuration-options-and-restrictions)
* [Mechanisms for starting workflow instances](/extension-apps/extension-apps-101/supported-extensions/file-output-tabular-format#mechanisms-for-starting-workflow-instances)

### Extension implementation details

Your implementation choices for the file output tabular format extension determine the details of how values are exported to files stored in cloud storage. See the next two sections for guidance.

#### External system logic to return file destination options

The file output tabular format extension supports capabilities that enable workflow process builders to select the file where the workflow variable values will be written. Below are the available options and the capabilities that enable each option.

| To enable the process builder to                                                | Implement this capability                       |
| ------------------------------------------------------------------------------- | ----------------------------------------------- |
| Select a drive or similar structure that contains folders and files.            | **List Drives**                                 |
| Select an existing file at any level in the directory structure.                | **List Directory Contents**                     |
| Select a drive or similar structure, and select an existing file in that drive. | **List Drives** and **List Directory Contents** |

If the extension enables the process builder to select a drive (or similar container type), Docusign sends the configured container and/or file path with **Export to Destination** requests at workflow instance runtime.

If the app does not implement capabilities to allow process builders to select a file destination, **Export to Destination** requests will include a file name only. The external system must implement logic to select a storage location. If the cloud storage system has a structure similar to Google Drive, Docusign recommends implementing both the **List Drives** and **List Directory Contents** capabilities.

See the file output tabular format extension contract for details about the request formats and the expected response formats. See [API proxy](/extension-apps/build-an-extension-app/it-infrastructure/api-proxy) for guidance on transforming requests and responses to the correct format.

#### External system logic to process Export to Destination requests

Docusign includes the workflow variables’ values, the file headers, and, optionally, a drive (or similar container type) and/or a file name in **Export to Destination** requests.

Some considerations for the external system logic to process these requests include:

* If the extension does not implement capabilities that enable a workflow process builder to specify a storage location, how will the external system select a location when it receives a request to write data to a file?

For details about the **Export to Destination** request and response formats, see the Export to Destination action contract. See [API proxy](/extension-apps/build-an-extension-app/it-infrastructure/api-proxy) for guidance on transforming requests and responses to the required format.

### Workflow configuration options and restrictions

Workflow Builder workflows are highly customizable and offer many possibilities for constructing the [steps in an agreement process](https://support.docusign.com/s/document-item?bundleId=yff1696971835267\&topicId=afu1730332596907.html). To export values to a tabular format, a workflow must be configured with a **File output step**, which invokes the file output tabular format extension. This step is available to workflows in any Docusign account that has the extension app [installed and connected](https://support.docusign.com/s/document-item?bundleId=ous1698169987748\&topicId=ctg1698170340729.html).

These restrictions apply when configuring a workflow to write data to tabular format files:

* The maximum number of variable values that can be exported to a tabular format from a workflow is 1,000.
* If values should be exported to multiple different files, the process builder must define a separate file output to tabular format step for each file.
* Not all variable types can be exported from a workflow. Checkboxes and radio groups are not supported in the current release.
* Values will be written to columns in the tabular format file from left to right in the order in which they are configured in the file output tabular format step. Process builders should ensure that the order in which they configure the variables matches the order of any existing columns in the destination file.
* For a file that has existing column headers, if the number of variables selected for export exceeds the number of column headers in the file, additional variable values will be written to new columns with generic headers like **Column 1**.

### Mechanisms for starting workflow instances

Docusign supports multiple options for starting workflow instances that export variable values to tabular format files. A workflow instance is a runtime execution of workflow steps that enables a customer to complete tasks such as filling out a form and signing an agreement.

To start workflow instances manually, see [How to Start a Workflow](https://support.docusign.com/s/document-item?bundleId=yff1696971835267\&topicId=glx1730400747416.html).

To start workflow instances programmatically, you can implement a Docusign Workflow Builder API integration that includes the [Workflows: triggerWorkflow](/docs/workflow-builder-api/reference/workflowbuilder/workflows/triggerworkflow) request. See [Workflow Builder API 101 overview](/docs/workflow-builder-api/workflow-builder101) for an introduction to the API, and [How to trigger a Workflow Builder workflow](/docs/workflow-builder-api/how-to/trigger-workflow) for example code and a detailed walkthrough.

## Next steps

* Get an overview of the process to [build an extension app](/extension-apps/build-an-extension-app).
* See [File output tabular format extension contract reference](/extension-apps/extension-app-reference/extension-contracts/file-output-tabular-format) for details about the action and capability requests and responses.
* Learn how to programmatically [trigger workflows](/docs/workflow-builder-api/how-to/trigger-workflow) that write files to cloud storage.