Skip to content
Book a Demo Open a Case

Salesforce apps by To A Finish

Four managed packages that run inside your own Salesforce org.

Simple Signature

Document creation and e-signatures in Salesforce

Address Verification

Clean, verify and geocode Salesforce addresses

Highlighter

Colors, renames or hides Salesforce fields

List Browse

Browse Salesforce records without list clicking

Get started

Install, configure and roll out a TAF package.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article per task

Book a demo

See a package in a live org

Compatibility

Editions and releases we support

Get help

Open a case and a person reads it.

Open a support case

The fastest route to an answer

Give us access

Let us sign in and see the problem

Support home

Guides, release notes and the case form

Troubleshooting

Search by the error text you see

Documentation

Written for admins, not for developers.

Implementation guides

Guides for all four apps are ready.

How-to articles

One task per article

Change log

What changed in each release

Compatibility

Editions and seasonal releases

Simple Signature Address Verification Highlighter List Browse Support Book a Demo
Simple Signature · How-to

Show the PDF in a Flow before the signature

How to do it in Simple Signature, one step at a time.

Last updated 9 Oct 2026

Paid version only. These steps do not count in the setup progress.

This screen Flow makes the Signature first. It waits for the PDF from a Google Docs template and shows it. Then it shows the form. The example starts from a Lead.

Before you start

Make a Google Docs template. Then add the parameter templates with its ID to the experience that this Flow uses. See Make a PDF template in Google Docs.

  1. Make a new Screen Flow.

    Do it the same way as in step 1 of Take signatures in a Flow.

  2. Make a variable named recordId.

    Click the Toolbox icon. Click Manager, then New Resource. Pick Variable. In API Name, type recordId, with exactly this case. Pick Text as the Data Type. Tick Available for input and Available for output. Click Done.

  3. Add a Get Records element for the Lead.

    Click the + on the line. Click Get Records. Type a Label. Pick Lead as the object. Add one filter: Lead ID Equals recordId. Leave the other settings as they are.

  4. Add a screen that tells the user what happens.

    Add a Screen. Type a Label. Drag Display Text onto it. Type an API Name for it, for example IntroText. Type the text, for example We are making your document. Then you can read it and sign.

  5. Add a Create Records element for the Signature.

    Type a Label. Pick Manually for how to set the field values. It starts on another choice. Pick ß Signature as the object. A search for Signature can show other objects first. Click Add Field for each row:

    FieldValue
    LeadThe variable recordId.
    Experience IDYour Experience ID.
    First Name, Last Name, EmailThe matching Lead fields, from the Get Records element.
    Attach PDF?{!$GlobalConstant.True}
    Embed PDF?{!$GlobalConstant.True}
    StatusRequested
    TemplatesThe ID of your template, the same as in the experience.
    Send TypeNone

    To also save the PDF on the Lead and email it, add Attach PDF to Parent? and Email PDF? with {!$GlobalConstant.True}.

  6. Add a screen with Simple Signature Wait.

    Add a Screen. Type a Label. Drag Simple Signature Wait onto it. Fill in its settings:

    SettingValue
    API NameA name, for example WaitPreview.
    Signature IdPick the Create Records element, then Record ID.
    Step IdLeave it empty. It serves signatures with steps.
    TypePreview. Final waits for the signed PDF instead.
  7. Add a screen with Simple Signature Preview. This step is optional.

    Add a Screen. Drag Simple Signature Preview onto it. In FileId, pick the Wait element, then fileId. Click Done.

  8. Add a screen with Simple Signature Form.

    Add a Screen. Open Configure Footer and untick Show Footer. Drag Simple Signature Form onto it. Fill in its settings:

    SettingValue
    Experience IDYour Experience ID.
    Parent IDThe variable recordId.
    Other ParametersType id= and the ID of the record from the Create Records element, for example id={!Create_Signature.Id}. Without it, the Flow makes a second Signature.
    StyleOptional.

    To show the PDF above the form, add &showattachmentid= and the fileId of the Wait element, for example id={!Create_Signature.Id}&showattachmentid={!WaitPreview.fileId}.

  9. Show the signed PDF too, if you want.

    Repeat steps 6 and 7 after the form, with Final as the Type.

  10. Save the Flow. Activate it.

    The finished Flow in Flow Builder: Get Records, the first screen, Create Records, and the Wait, Preview and Form screens.
  11. Make a Flow action on Lead. Add it to the page layout.

    Open Object Manager. Click Lead, then Buttons, Links, and Actions. Click New Action. Pick Flow as the Action Type. Pick your Flow. Type a Label. Click Save.

    Add the action to the Lead page layout, the same way as in step 5 of Send a signature request.

  12. Open a test Lead. Start the Flow from the action.

    The Flow does not run from Flow Builder. Start it from a Lead in Lightning Experience.

    The Flow makes the Signature and waits for the PDF. A spinner shows while it waits, for up to a minute. Then the PDF shows. Click Next. If the first click only zooms the PDF, click Next again.

    With Require eSignature Agreement on, the agreement window opens before the form.

    The Flow window with the PDF from the Google Docs template, before the form.

Applies to

Simple Signature 5.8.x, paid version. These steps come from the tested Simple Signature implementation guide, where they sit with the steps before and after them.

Was this helpful?

Related

Support

Still stuck?

Open a case and paste the exact error text. A person reads every case.