> 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

# Identify the file source (beta)

> Review the options for the source of files to write to a system of record.

The file output system of record extension supports two sources for files to export: a **Send Documents for Signature** workflow step, or any envelope sent from the account that meets certain conditions. See the next sections for details.

## Send Documents for Signature workflow step

During workflow configuration, a process builder can select a [Send Documents for Signature step](https://support.docusign.com/s/document-item?bundleId=yff1696971835267\&topicId=uww1698167288211.html) as the source for files that will be exported in a **File Output** step. The **Send Documents for Signature** step setup defines the content and delivery method for [eSignature envelopes](https://support.docusign.com/s/document-item?bundleId=oeq1643226594604\&topicId=ghu1578456429097.html).

During workflow instance execution, the **Send Documents for Signature** step generates an envelope, which the customer completes and signs. The **File Output** step exports the envelope's documents to the system of record.

Use this option if the file export requirements are specific to the [eSignature template](https://support.docusign.com/s/document-item?bundleId=xry1643227563338\&topicId=dqj1578456412286.html\&rsc_301) and agreement process defined in the workflow. This option supports exporting all the files associated with an envelope as a single PDF. For a choice of export formats, or if the export requirements apply more broadly to envelopes sent from the account instead of from a specific workflow, the option described in the next section may be a better choice.

See [File output system of record test: Workflow step creates envelopes](/extension-apps/build-an-extension-app/test/functional-tests/file-output-system-of-record-workflow-step-creates-envelopes) for details about workflow setup.

## Envelopes sent from the account

During workflow configuration, a process builder can set the workflow [start method](https://support.docusign.com/s/document-item?language=en_US\&bundleId=yff1696971835267\&topicId=ztb1727892686033.html) to **From an Event**. This start method triggers a workflow instance for any envelope sent from the account if the envelope meets certain conditions. For example, the process builder can specify that workflow instances start on completion of envelopes created from a specific template. When this option is used, the process builder also configures the **File Output** step to use the instance-triggering envelopes as the source of files to write to the system of record.

At runtime, an envelope event that meets the workflow start requirements triggers the execution of a workflow instance. The **File Output** step exports the envelope's documents to the system of record.

Use this option if file export is broadly applicable to envelopes being sent from the account, possibly via multiple mechanisms (for example, envelopes sent manually from the eSignature web application and envelopes sent programmatically via an eSignature API integration). In addition, this option supports exporting envelope files individually, as a ZIP file containing the individual envelope files, or as a single PDF that includes the contents of all the files. The process builder can select one of these options during **File Output** step configuration.

See [File output system of record test: An event triggers the workflow](/extension-apps/build-an-extension-app/test/functional-tests/file-output-system-of-record-event-triggers-workflow) for details about workflow setup.

## Next steps

* Learn more about [setting up workflows](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/workflow-configuration) that include file output to system of record.
* See how the file output system of record [extensions and actions](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/extensions-and-actions) function during workflow configuration and execution.
* Get an overview of the process to [build an extension app](/extension-apps/build-an-extension-app).