Skip to main content

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’s 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:
  • Vault — saves one or more files into a specified Vault folder
  • Contracts — saves files into the Contracts repository; flow variables can be mapped to contract metadata with Map Fields
  • Salesforce — writes flow data back to a record. Select the primary object by its Salesforce Record ID, then map flow variables to the fields you want to update

Files to Store

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

Field Mapping

Available for Contracts and Salesforce destinations, via Map Fields. For Contracts this populates contract metadata; for Salesforce, select the source variable and the Salesforce field to update.

Example

A flow generates an MSA and collects a signed copy. The Store step is configured with Destination: Contracts, Files to store: @Generate1.Document, and field mapping “Customer Name” → @Intake.CustomerName, “Contract Term” → @Intake.ContractTerm. The signed MSA is saved to the Contracts repository with those fields populated from Intake.
Store doesn’t create a task or output document. A single flow can include multiple Store steps writing to different destinations, and it’s typically placed at the end of a flow after documents are generated, negotiated, or signed. For Salesforce, the primary object must be identified by its Salesforce Record ID.