> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/s-sign/automation-and-envelope-lifecycle/automate-e-signature-with-flow-builder.md).
# 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
***
{% columns %}
{% column %}
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### 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
{% hint style="info" %}
The process outlined throughout this guide will be mimicked for generic auto-launched flows.
{% endhint %}
***
### Phase 1: Collect the Data
{% columns %}
{% column %}
Use the **Get Records** Invocable Action to gather the object record. Use Filters to limit what records are collected.
{% hint style="info" %}
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:
{% endhint %}
{% endcolumn %}
{% column %}
Use the **Get Records** Invocable Action to gather the S-Docs Template. Use Filters to limit which record is collected.
{% hint style="info" %}
Template IDs are unique to an Organization. If migrating templates from one Organization to another, be sure to change the ID within the Flow.
{% endhint %}
{% endcolumn %}
{% endcolumns %}
***
### 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
{% columns %}
{% column %}
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**
{% endcolumn %}
{% column %}
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**
{% endcolumn %}
{% endcolumns %}
***
### 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
* Field-level action details: [Flow Reference (Prepare Envelope)](/developer-hub/document-workflows/flow-reference.md#prepare-envelope)
* Field-level action details: [Flow Reference (Seal Envelope)](/developer-hub/document-workflows/flow-reference.md#seal-envelope)
* **Prepare Envelope** must receive the generated document from your earlier step.
* **Seal Envelope** returns the `signingLink` output.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.sdocs.com/s-sign/automation-and-envelope-lifecycle/automate-e-signature-with-flow-builder.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
