> 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/send-e-signature-requests-from-a-record-triggered-flow.md). # Send E-Signature Requests from a Record-Triggered Flow
Use this guide when you want Salesforce to send an S-Sign request automatically. Use this pattern when a record change should trigger document generation and delivery. 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. **Send** out the request for Electronic Signature This pattern is close to a standard Flow Builder automation. The key requirement is the asynchronous path. Move all document generation, envelope, and email actions there. #### Start here if you are newer to Flow New to Flow? Start with [Getting Started: Automate Document Generation](/quick-start/document-generation/getting-started-automate-document-generation.md). If you need the base action pattern, use [Automate E-Signature with Flow Builder](/s-sign/automation-and-envelope-lifecycle/automate-e-signature-with-flow-builder.md). ### Prerequisites * Access to **Flow Builder** * A **Record-Triggered Flow** * An **S-Sign Enabled** template * A record condition that should trigger the request * S-Docs actions available in your org * Permission to create generated documents and envelopes {% hint style="info" %} **Admin Note:** Don't let the word "Apex" worry you. These S-Docs actions are included out of the box. You simply select them from the Flow action list. {% endhint %} ### Step-by-step tutorial #### Step 1: Configure the record trigger
Create a **Record-Triggered Flow** for the object that should launch the request. Define these values in **Start**: * the object to monitor * when the trigger runs * the entry conditions Only use conditions that clearly identify when the request should be sent. This prevents duplicate envelopes and accidental sends. #### Step 2: Add the asynchronous path
Set the flow to **Optimize the Flow for Actions and Related Records**. Then enable **Add Asynchronous Path**. Place all S-Docs actions on the asynchronous path. That includes: 1. **Get Records** 2. **Generate Document** 3. **Prepare Envelope** 4. **Seal Envelope** 5. **Send Email** {% hint style="warning" %} Do not place **Generate Document**, **Prepare Envelope**, **Seal Envelope**, or **Send Email** on the immediate path. {% endhint %} #### Step 3: Build the S-Sign sequence on the asynchronous path Build the asynchronous branch using the same action order as the Screen Flow pattern. Use [Automate E-Signature with Flow Builder](/s-sign/automation-and-envelope-lifecycle/automate-e-signature-with-flow-builder.md) for the full action-by-action setup. Map the current record into your lookup steps and action inputs. In a record-triggered flow, the base record usually comes from `$Record.Id`. Confirm each action receives the required output from the prior step. For example: * **Generate Document** needs the base record and template * **Prepare Envelope** needs the generated document * **Seal Envelope** needs `Envelope Id` * **Send Email** needs the sealed envelope context and attachment collection ### Troubleshooting and common errors
The flow runs, but no S-Sign request is sent * **Symptom:** The record updates, but no document or envelope is created. * **Cause:** The entry conditions do not match, or the S-Docs actions are not on the asynchronous path. * **Fix:** Recheck the trigger conditions. Confirm all S-Docs actions are under the asynchronous branch.
The flow faults during document or envelope actions * **Symptom:** The flow errors on **Generate Document**, **Prepare Envelope**, or **Seal Envelope**. * **Cause:** A required ID or prior output is blank. * **Fix:** Confirm each step maps the correct value from the prior step. Add a **Fault** path to each action for easier debugging.
The wrong records are used in the request * **Symptom:** The generated document uses the wrong template or record data. * **Cause:** The **Get Records** filters are too broad, or the base record input is wrong. * **Fix:** Tighten the **Get Records** filters. Confirm the flow uses `$Record.Id` where the current record is required.
### Advanced configurations and reference * Base pattern: [Automate E-Signature with Flow Builder](/s-sign/automation-and-envelope-lifecycle/automate-e-signature-with-flow-builder.md) * 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) * **Record-Triggered Flow** must use an asynchronous path for S-Docs actions. * Use `$Record.Id` when the action should use the record that triggered the flow. * Add **Fault** paths to **Generate Document**, **Prepare Envelope**, **Seal Envelope**, and **Send Email**. * Confirm the action order stays the same from start to finish. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.sdocs.com/s-sign/automation-and-envelope-lifecycle/automate-e-signature-with-flow-builder/send-e-signature-requests-from-a-record-triggered-flow.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.