> 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 destination records (beta)

> Review the options for identifying records to which files will be written.

The file output system of record extension supports two options for identifying the record that a file will be written to: a workflow variable value or a record ID returned from a **Read from** workflow step. See the next sections for details.

## Use a workflow variable value

During workflow [File Output step](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record#workflow-step-that-exports-files) configuration, the process builder can select a workflow variable to use as the record identifier. The variable can represent a value that:

* Is passed to the workflow from an API integration that triggered the workflow
* Identifies the customer, such as their name or email address
* The customer enters during a previous workflow step, such as a [Send Documents for Signature step](https://support.docusign.com/s/document-item?bundleId=yff1696971835267\&topicId=uww1698167288211.html)

The process builder also selects the object in the system of record that the file will be written to.

At runtime, when a workflow instance reaches the **File Output** step, Docusign sends a [Write File](/extension-apps/extension-app-reference/extension-contracts/file-output-system-of-record#write-file) request to the external system. The request includes the object the process builder selected and the variable value as the record identifier.

For additional details about configuration and runtime execution, see [Extensions and actions: Record identifier is a workflow variable](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/extensions-and-actions#extensions-and-actions-record-identifier-is-a-workflow-variable).

This option for selecting a record identifier is easier for workflow process builders to configure. However, it requires that the external system use a single workflow variable value, along with an object name, to uniquely identify a record to write files to. If this is not feasible, you can instead identify a record using a **Read from** workflow step, as described in the next section.

## Use an ID returned by a Read from workflow step

During workflow configuration, a process builder can include a **Read from** step that defines a search query to the external system. The query identifies the record to write a file to and returns the record ID. When the process builder configures the **File Output** step, they select the ID returned by the **Read from** step as the record identifier.

At workflow instance runtime, the **Read from** step execution sends a query to the external system, which returns the ID of the record to write the file to. Docusign includes this ID in the request it sends to the external system when the **File Output** step is executed.

For additional details about configuration and runtime execution, see [Extensions and actions: Record ID is from a Data read step](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/extensions-and-actions#extensions-and-actions-record-id-is-from-a-data-read-step).

Use this option if you need more than a single workflow variable value to identify the record to write a file to. For example, if a customer name, email address, and account number are all required to uniquely identify a destination record, a process builder can configure a **Read from** step that launches a query that uses all three values. You may also prefer this option if other steps in a workflow, such as a [Collect Data with Web Forms step](https://support.docusign.com/s/document-item?bundleId=yff1696971835267\&topicId=gua1698120920620.html), require values to be retrieved from the record in the external data source. In this case, you can configure the **Read from** step so that it returns multiple values from the data source record, in addition to the ID of the record that the files are to be written to.

## Impact on implementation

The choice of how to identify records to write to determines which [extensions](/extension-apps/extension-apps-101/concepts/extensions-and-extension-points) and [actions](/extension-apps/extension-apps-101/concepts/actions) your app must implement, so it should be made early in your development planning process.  The required extensions and actions for each option are listed below.

| Record identifier                            | Required extension(s)                                                                                                                                                                                       | Required actions                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Notes                                                                                                                                                                  |
| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A workflow variable value                    | [File output system of record](/extension-apps/extension-app-reference/extension-contracts/file-output-system-of-record)                                                                                    | File output:- [Get Type Names](/extension-apps/extension-app-reference/extension-contracts/file-output-system-of-record#get-type-names) capability
- [Write File](/extension-apps/extension-app-reference/extension-contracts/file-output-system-of-record#write-file) action                                                                                                                                                                                                                                                                         | The inclusion of the **Get Type Names** capability causes the **File Output** step configuration panel to display a dropdown for selecting the external system object. |
| A record ID returned by a **Read from** step | [Data IO](/extension-apps/extension-app-reference/extension-contracts/data-io) and [File output system of record](/extension-apps/extension-app-reference/extension-contracts/file-output-system-of-record) | Data IO:- [Get Type Names](/extension-apps/extension-app-reference/extension-contracts/data-io#dataio-version6-get-type-names) action
- [Get Type Definitions](/extension-apps/extension-app-reference/extension-contracts/data-io#dataio-version6-get-type-definitions) action
- [Search Records](/extension-apps/extension-app-reference/extension-contracts/data-io#dataio-version6-search-records) action File output:
- [Write File](/extension-apps/extension-app-reference/extension-contracts/file-output-system-of-record#write-file) action | The inclusion of the data IO extension makes the **Read from** step available in the workflow.                                                                         |

For additional information, see:

* [Workflow configuration for file output scenarios](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/workflow-configuration) for details about workflow setup.
* [Extensions and actions](/extension-apps/extension-apps-101/supported-extensions/file-output-system-of-record/extensions-and-actions) to learn about the required extension app components.

## Next steps

* 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).
* 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.
* Get an overview of the process to [build an extension app](/extension-apps/build-an-extension-app).