> 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 system of record extension overview (beta)

> Learn about how files generated from Docusign workflows can be written to a system of record in real time.

The file output system of record extension exports documents to a system of record in real time as customers complete them. For example, the extension can be invoked from a [workflow](https://support.docusign.com/s/document-item?bundleId=yff1696971835267\&topicId=dnx1696972415150.html) that sets up electronic funds transfer (EFT) for investment accounts. After customers sign EFT authorization forms, the extension sends a request to the system of record to write the files to the specified object and record.

> **Note**
>
> Docusign offers extension apps that integrate with HubSpot, Microsoft Dynamics 365, and Salesforce. If you want to store files to these services, visit the [Docusign App Center](https://apps.docusign.com/app-center) for details.

## Workflow step that exports files

After a file output to system of record extension app has been [installed and connected](https://support.docusign.com/s/document-item?bundleId=ous1698169987748\&topicId=ctg1698170340729.html) to a Docusign account, workflows in the account can write files to a system of record. To use this feature, a workflow must include a **File Output** step that invokes the extension.

**File Output** and other workflow steps have two phases of operation:

1. **Workflow configuration:** A workflow process builder in your or your customer's organization creates a workflow. During this one-time setup, the process builder adds workflow steps and defines properties that determine each step's runtime behavior. For example, when a process builder defines a **File Output** step, they select the file source, the destination object, a value that identifies the record to write the file to, and a file naming convention.
2. **Workflow instance execution:** A workflow instance is a runtime execution of a workflow's steps for a specific customer. Each instance includes customer-specific workflow variable values that can be used in the steps. For example, when workflow instance execution reaches a **File Output** step, a customer's account number can be sent as a record identifier in the request to write the file to the system of record. The request also includes the object that the process builder selected during workflow configuration.

Additional workflow steps or configuration may be required along with the **File Output** step. This depends on how your implementation identifies the destination record for the write operation and how the workflow obtains files to write. These topics explain the options:

* [Identify destination records](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/identify-destination-records)
* [Identify the file source](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/identify-file-source)

The next section provides an example of how the file output system of record extension functions during workflow configuration and instance execution.

## Use a file output system of record extension in a workflow

In the example described here, a process builder defines a workflow that enables a customer to authorize EFT for a financial account.

Expand the sections below to see how a file output system of record extension functions during workflow configuration and execution. See [Extensions and actions](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/extensions-and-actions) for details about the functionality.

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

When adding a workflow step to write files to a system of record, the process builder selects the extension that has been installed to their Docusign account.

![Add file output step](/_fern-files/_img/4483c5d70fd83fa9dc5a496706ad06ee1d50c98cf19fab38f2886c67f10d391a.webp)

#### Workflow configuration: The process builder selects the file source

The process builder configures the file output step. The setting shown here determines the source of files to export to the system of record. In this example, the source is an eSignature [envelope](https://support.docusign.com/s/document-item?bundleId=ulp1643236876813\&topicId=gso1578456465211.html), which is generated during a workflow [Send Documents for Signature step](https://support.docusign.com/s/document-item?bundleId=yff1696971835267\&topicId=uww1698167288211.html). A combined envelope file is a PDF that contains the envelope documents that a customer completed and signed.

![Select a file source](/_fern-files/_img/a70a64fc13dde3c9a03c2b90cdf04c9b04279f194473fd7b92f69153c1db02b1.webp)

#### Workflow configuration: The process builder selects the file destination

Next, the process builder selects a destination in the system of record for files to be exported.

In the **Select record** list, the process builder chooses a workflow variable whose runtime value will be sent with the request to write the file. In this example, the variable is an envelope field that contains the customer account number. The external system can use this value to identify the record to write the file to.

To populate the **Object** list, Docusign invokes the file output system of record extension to retrieve a list of system of record objects that files can be written to. The object name that the process builder selects will be included with the request to write the file.

![Select a file destination](/_fern-files/_img/a2125eeafdd7f7d1fa090474a9a63bda0bc3004ec271c2782b8c3cd9c24ec6fd.webp)

#### Workflow configuration: The process builder defines a file naming convention

The process builder defines a naming convention for files that are written to the system of record. File names can consist of hardcoded text, variables whose values are specific to each workflow instance (such as the envelope ID or signer name), or a combination of the two.

![Select a file naming convention](/_fern-files/_img/f88425bdd0bfcabc682ca5c284b0cac24ae99a9da7f0a79e0da91ebf5eb9e9cb.webp)

#### Workflow instance execution: The customer completes an envelope

When workflow instance execution reaches the **Send Documents for Signature** step, the customer completes and signs the envelope that contains the EFT authorization form.

![eSignature envelope](/_fern-files/_img/e32e9c1a061a639146ffb8cc5ac4b63918b8b1d53e93799c92a79cc97a6d80ad.webp)

#### Workflow instance execution: The file is written to the system of record

After the customer has completed the envelope, the workflow instance reaches the **File Output** step. The file output system of record extension is invoked to write the envelope file to the system of record. The external system uses the object name and workflow variable value provided in the request to identify the destination for the file.

![Output to the data source](/_fern-files/_img/9ebf2a4b6be89a830349b1a6cbf2b7937518b63612682244b43d0a3bde9966af.webp)

## Next steps

* Review the options for [identifying a destination record](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/identify-destination-records) to which a file will be written.
* See the choices available to select as the [file source](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/identify-file-source).
* Get an overview of the process to [build an extension app](/extension-apps/build-an-extension-app).

> Learn about how files generated from Docusign workflows can be written to a system of record in real time.

## Docs

- [Identify destination records (beta)](https://developers.docusign.com/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/identify-destination-records.md): Review the options for identifying records to which files will be written.
- [Identify the file source (beta)](https://developers.docusign.com/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/identify-file-source.md): Review the options for the source of files to write to a system of record.
- [Workflow configuration for file output scenarios (beta)](https://developers.docusign.com/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/workflow-configuration.md): Review workflow configuration options for various file output scenarios.
- [Extensions and actions (beta)](https://developers.docusign.com/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/extensions-and-actions.md): Review the extensions and actions associated with file output to system of record.
- [Plan an implementation (beta)](https://developers.docusign.com/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/plan-implementation.md): Learn about important considerations when planning a file output to system of record implementation.