# Automate E-Signature with Schedule-Triggered Flows

<figure><img src="/files/5t4D6ninZjZhfjNrxeQ5" alt=""><figcaption></figcaption></figure>

***

### Understanding the Overall Schema

Outlined above is the generalized process from start to finish users will take to generate an S-Sign Request using a Schedule-Triggered Flow.&#x20;

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

This process shares many similarities to the Screen-Flow or Record-Triggered Flow when generating E-Signature Requests. The key discrepency being how the flows are initiated. A screen flow must be initiated through a separate action, such as button or Lightning Web Component. A Record-Triggered Flow will initiate when a record is created or updated based on the configured filters. A Schedule-Triggered Flow initiates when the configured time is reached.&#x20;

***

### Phase 1: Configure the Schedule Trigger

<figure><img src="/files/ezrqaLFCzNW6Dr3sqWWy" alt="" width="563"><figcaption></figcaption></figure>

A scheduled-triggered flow will need to have conditions set in order to function.&#x20;

1. **Define the Start Date** that will trigger the flow to run
2. **Define the Start Time** that the flow will be ran at
3. **Define the Frequency** that the flow will reoccur&#x20;

***

### Phase 2: Construct the Flow&#x20;

1. Construct the Flow using the same process outlined in [Automate E-Signature with Flow Builder](/s-sign/automation-and-envelope-lifecycle/automate-e-signature-with-flow-builder.md)


---

# Agent Instructions: 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:

```
GET https://help.sdocs.com/s-sign/automation-and-envelope-lifecycle/automate-e-signature-with-flow-builder/automate-e-signature-with-schedule-triggered-flows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.