Launch Sign in Person from a Screen Flow

Use a Screen Flow to generate an envelope, seal it, and display the live signing link for an in-person signing session.

Use this guide when you want a Screen Flow to launch an in-person signing session.

Use this pattern when the signer is present on the same device.

The flow follows this order:

1. Collect Data that will be used for document generation (S-Sign Enabled Template + Object Record)
2. Generate the document from the collected data
3. Prepare the Envelope the generated document will be stored in
4. Seal the Envelope in preparation to deliver the request
5. Display the signing link to the active signer

This pattern is close to a standard email-based S-Sign flow.

The main difference is the final step.

Instead of sending an email first, the flow shows the live signing link.

Start here if you are newer to Flow

New to Flow? Start with Getting Started: Automate Document Generation.

If you need the base action pattern, use Automate E-Signature with Flow Builder.

Prerequisites

• Access to Flow Builder
• An S-Sign Enabled template
• A Screen Flow
• A generated document step before Prepare Envelope
• A screen step placed after Seal Envelope

Admin Tip: If this flow runs from a record page, create a Text variable named recordId. This name is case-sensitive. Then enable Available for input.

Step-by-step tutorial

Step 1: Enable Sign in Person on Prepare Envelope

Add Prepare Envelope after your document generation step.

Map the generated document into the envelope input.

Set Sign In Person to True.

This tells S-Sign to create an in-person session.

Admin Note: The screen link does not come from Prepare Envelope. It comes from Seal Envelope.

Step 2: Seal the envelope

Add Seal Envelope after Prepare Envelope.

Map Envelope Id from the Prepare Envelope output.

This step activates the envelope and creates the live signing session.

The signing link becomes available only after this step runs.

Admin Note: The signingLink output is generated by Seal Envelope. You will use that output in the next step.

Step 3: Add a screen after Seal Envelope

Add a Screen element after Seal Envelope.

Use this screen to present the signer with the live session link.

Do not place the screen before Seal Envelope.

If you do, the link will be blank.

Step 4: Add the live signing link to Display Text

Inside the screen, add a Display Text component.

Add your message and insert a link.

Set Link URL to:

{!Seal_Envelope.signingLink}

Use the Seal Envelope action API name that exists in your flow.

If you renamed the action, use that API name instead.

Troubleshooting and common errors

The signing link is blank

• Symptom: The screen loads, but the link has no value.
• Cause: The screen runs before Seal Envelope, or the wrong output is mapped.
• Fix: Move the screen after Seal Envelope. Use signingLink from that action.

The signer gets an email instead of signing on the device

• Symptom: The request starts as a standard email flow.
• Cause: Sign In Person is not set to True, or the flow still sends the email immediately.
• Fix: Set Sign In Person to True. Remove or delay the initial email action.

The flow faults during envelope setup

• Symptom: The flow stops on Prepare Envelope or Seal Envelope.
• Cause: A required ID is missing.
• Fix: Confirm the generated document feeds Prepare Envelope. Confirm Envelope Id feeds Seal Envelope. Add a Fault path to each action.

Advanced configurations and reference

• Field-level action details: Flow Reference (Prepare Envelope)
• Field-level action details: Flow Reference (Seal Envelope)
• Prepare Envelope must receive the generated document from your earlier step.
• Sign In Person must be True.
• Seal Envelope returns the signingLink output.
• Use Seal_Envelope.signingLink only if Seal Envelope uses that API name.
• Add Fault paths from Prepare Envelope and Seal Envelope to an error screen.