Send E-Signature Requests from a Schedule-Triggered Flow

Use a Schedule-Triggered Flow to generate, seal, and send S-Sign requests on a recurring schedule.

Use this guide when you want Salesforce to send S-Sign requests at a scheduled time.

Use this pattern for recurring jobs, timed follow-up workflows, or batch-style 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 uses the same S-Sign action sequence as other Flow automations.

The main difference is how the flow starts.

A Schedule-Triggered Flow runs at the time and frequency you define.

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
• A Schedule-Triggered Flow
• An S-Sign Enabled template
• A clear schedule for when the flow should run
• Filters that identify which records should be processed
• S-Docs actions available in your org
• Permission to create generated documents and envelopes

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.

Schedule-triggered flows can process many records in one run. Keep your filters narrow and test with a small record set first.

Step-by-step tutorial

Step 1: Configure the schedule

Create a Schedule-Triggered Flow.

In Start, define:

• the Start Date
• the Start Time
• the Frequency

Choose a schedule that matches when records should be processed.

Use a frequency that avoids duplicate sends.

Step 2: Define which records to process

Add filters that return only the records that should receive a request.

Be explicit about status, date, and readiness conditions.

This keeps the flow from sending envelopes too early or too often.

If the flow should process a single object type on each run, keep the object scope narrow.

Step 3: Build the S-Sign sequence

Build the action sequence in this order:

1. Get Records
2. Generate Document
3. Prepare Envelope
4. Seal Envelope
5. Send Email

Use Automate E-Signature with Flow Builder for the full action-by-action setup.

Confirm each step 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

Do not place Generate Document inside a Loop unless the design explicitly requires one envelope per loop item. Large scheduled runs can hit Flow limits quickly.

Troubleshooting and common errors

The flow runs, but no S-Sign requests are sent

• Symptom: The scheduled job runs, but no documents or envelopes are created.
• Cause: The schedule is active, but the record filters return no records.
• Fix: Review the object filters and test them against live records. Confirm the scheduled time has passed and the records meet the criteria at runtime.

The same record gets processed more than once

• Symptom: A record receives duplicate S-Sign requests on later runs.
• Cause: The flow has no field or filter that marks the record as already processed.
• Fix: Add a status field, date field, or other control value. Update it after the request is sent. Exclude processed records from future runs.

The flow faults during document or envelope actions

• Symptom: The flow errors on Generate Document, Prepare Envelope, Seal Envelope, or Send Email.
• Cause: A required ID or prior output is blank.
• Fix: Confirm each action maps the correct value from the prior step. Add a Fault path to each action for easier debugging.

Advanced configurations and reference

• Base pattern: Automate E-Signature with Flow Builder
• Field-level action details: Flow Reference (Prepare Envelope)
• Field-level action details: Flow Reference (Seal Envelope)
• Schedule-Triggered Flow runs at the time and frequency set in Start.
• Use filters that exclude records that were already processed.
• Add Fault paths to Generate Document, Prepare Envelope, Seal Envelope, and Send Email.
• Confirm the action order stays the same from start to finish.