Skip to main content

Pre-fill native e-signature fields with LeadSimple data

Use Prefill from to insert built-in or custom-field values into an agreement and control whether the signer may edit them.

V
Written by Vitor Ferreira

Prefill from inserts an existing LeadSimple value into an agreement when a workflow sends it. For example, you can prefill a tenant name or a monthly rent amount.

Prefilling and saving signer answers are separate settings. Prefilling copies a value into the agreement; it does not, by itself, save any changes the signer makes back to LeadSimple.

Before you begin

  • Create and publish a native document template with the fields you need.

  • Give independently mapped questions distinct document-field names.

  • Make sure the source values exist on the records your workflow will use.

Configure a prefill

  1. Open the workflow settings for the pipeline or process type.

  2. Open the E-signature step's Configure E-Signature dialog.

  3. On Document, select the ready native template. Configure the required roles on Signer Routing.

  4. Open Field Mapping.

  5. Find the document field and its signer role.

  6. In Prefill from, search for and choose the LeadSimple value to insert. Available choices depend on the workflow and its record context and can include built-in fields and custom fields.

  7. Set the padlock beside the prefill selector. A closed padlock prevents the signer from editing the prefilled value. An open padlock allows edits.

  8. Select Save E-Signature Step.

Field Mapping showing Tenant.Full Name and Process.Monthly Rent in Prefill from with locked padlocks.

Prefill from supplies existing record values. The padlock controls whether the signer may edit them.

Example

For a document field called Monthly rent, choose the corresponding saved rent field under Prefill from. Keep it locked when the signer should only review the agreed amount. Leave a separate question, such as Move-in instructions, without a prefill when you want the signer to provide a new answer.

Check the result

Use the lead's E-signature task review to inspect prefilled values when a preview is available. Check the source data directly on process records, and test your configuration with an internal example before using it for customers.

  • A missing value for a required mapped document field blocks sending.

  • A field with no prefill source is completed by the signer.

  • Choose compatible field types: for example, a Number field for an amount and a Date field for a date. A Text field is useful when the agreement must show a formatted value such as a currency label.

  • The padlock has no effect until a prefill source is selected.

Scope of this guide

These instructions cover workflow-based prefilling. A standalone request from the Signatures page does not automatically resolve lead/process workflow mappings. Changes made to a source record after sending do not update an issued agreement.

Did this answer your question?