Store

Last updated: March 22, 2026

Overview

The Store step saves documents or data from your flow to an external destination. It persists flow outputs — such as generated or signed contracts — into Chamelio's Vault, the Contracts repository, or Salesforce.

Use Store when you need to write the results of a flow to a system of record. It does not create a task or produce a new output document — it is a write-only step.

Use When

  • You want to save a generated or signed document to the Vault or Contracts repository

  • You need to write flow data back to a Salesforce record after processing

  • You're archiving finalized agreements at the end of a workflow

  • You want to map extracted or collected data to fields in an external system

Configuration Options

Store Destination

Choose where the output should be stored. Three destinations are available:

  • Vault: Saves one or more files from the flow into a specified folder in the Documents Vault. Select the files to store and the target Vault destination.

  • Contracts: Saves one or more files from the flow into the Contracts repository. You can also map flow variables to contract metadata fields using the Map Fields option.

  • Salesforce: Writes flow data back to a Salesforce record. Select the primary object by its Salesforce Record ID, then map flow variables to the Salesforce fields you want to update.

Files to Store

Available for Vault and Contracts destinations. Select which files from the flow to save — these can be documents produced by a Generate step, collected during a Collect step, or attached at Intake. Multiple files can be added using Add File.

Field Mapping

Available for Contracts and Salesforce destinations. Map flow variables to destination fields using the Map Fields option. For Contracts, this populates contract metadata. For Salesforce, select the source variable and choose which Salesforce field to update.

Example

Configuration

A flow generates an MSA and collects a signed copy. The Store step is configured with:

  • Destination: Contracts

  • Files to store: @Generate1.Document

  • Field mapping: "Customer Name" → @Intake.CustomerName, "Contract Term" → @Intake.ContractTerm

Result

The signed MSA is saved to the Contracts repository with the customer name and contract term populated from the Intake data.

Notes

  • Store does not create a task or output document

  • Multiple files can be stored in a single Store step using Add File

  • For Salesforce, the primary object must be identified by its Salesforce Record ID

  • Store is typically placed at the end of a flow, after documents have been generated, negotiated, or signed

  • A single flow can include multiple Store steps to write to different destinations