Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Automate E-Signature with Flow Builder

This page will walk our S-Docs Users through constructing a screen flow that will allow for Document Generation, Envelope Creation, and Electronic Delivery, a guide to Automate E-Signature requests

Understanding the Overall Schema

Outlined above is the generalized process from start to finish users will take to generate an S-Sign Request.

The process goes as follows:

  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. Send out the request for Electronic Signature

The process outlined throughout this guide will be mimicked for generic auto-launched flows.

Phase 1: Collect the Data

Use the Get Records Invocable Action to gather the object record. Use Filters to limit what records are collected.

If the flow is initiated by a LWC or Button on the object record, create and use the {!recordId} standard resource from Salesforce. For more information, please visit Salesforce's Article here: https://help.salesforce.com/s/articleView?id=service.omnichannel_create_recordid.htm&type=5

Use the Get Records Invocable Action to gather the S-Docs Template. Use Filters to limit which record is collected.

Template IDs are unique to an Organization. If migrating templates from one Organization to another, be sure to change the ID within the Flow.

Phase 2: Generate the Document

Using the Generate Document Invokable Action, provide the Base Record ID and the S-Docs Template ID gathered in Phase 1.

Create a new variable named SSLinkGeneration

  • Create: Variable

  • Data Type: Text

  • Check: Allow Multiple values (collection)

Using the Assignment Action, assign the Generated S-Docs ID that was generated in previously to the collection. The SSLinkGeneration collection will be provided as an attachment when the email is delivered.

Phase 3: Create the Envelope, Seal the Envelope

Using the Prepare Envelope Invocable Action, store the Generated S-Docs ID from Phase 2

Under Advanced Options set the Transaction Control to Always start a new transaction

Using the Seal Envelope Invocable Action, store the Envelope Id from the previous step.

Under Advanced Options set the Transaction Control to Always start a new transaction

Phase 4: Deliver the E-Signature Request

Using the Send Email Invocable Action, provide the Base Record ID, the S-Sign Enabled Email Template, and the SSLinkGeneration collection. The Recipients Email Address will be pulled from the email defined by the Signer Profile within the S-Docs Template.

Advanced configurations and reference