Pattern one
Send when the stage changes
A record-triggered Flow watches the Opportunity. When the stage moves to the one you nominate, the action fires and the contract goes out with record data already merged in.
Salesforce Flow eSignature actions that send, route and file every agreement without code
Trigger the signature request from a Flow, no developer needed. Drop the action onto the canvas, pass it a record, and let the signed event update your fields and file the PDF.
Reference
Salesforce Flow eSignature: one invocable action, six inputs, two outputs.
The Send for signature action appears in the Flow element list like any standard action. Fill the inputs from record variables, store the outputs, and carry on building.
Inputs
| Input | Type | What it does |
|---|---|---|
| recordId | Text | The record the request belongs to. Sets where status is shown and where the signed PDF is filed. |
| templateId | Text | The prepared document to send, with its fields already placed. |
| recipients | Collection | One or more signers, by email address or by contact record. |
| roles | Collection | The role each recipient plays, which decides the fields they see and the order they sign in. |
| mergeData | Collection | Record values to merge into the document before it goes out. |
| expiryDays | Number | How long the request stays open before it is marked expired. |
Outputs
| Output | Type | What you do with it |
|---|---|---|
| requestId | Text | Store it on the record so later Flows and reports can find this request. |
| status | Text | Sent, Viewed, Signed, Declined or Expired. Branch on it anywhere in your automation. |
The same action works in record-triggered, schedule-triggered and screen Flows, so a rep can also launch it from a screen when the moment calls for a human decision.
Three patterns that cover most no-code signature workflows.
Build them in an afternoon, and every agreement after that routes itself.
Add the SignSecure action to a record-triggered flow and a signature request goes out the moment a stage changes, with no Apex and no callout to write.
Pattern two
Approve first, then send
Your approval process runs as it always has. The moment the record is approved, the Flow picks it up and sends for signature, so the gap between yes and out the door disappears.
Pattern three
Handle the signed event
When the request comes back signed, a second Flow updates your fields, files the sealed PDF where you want it, and posts the next task to whoever picks the work up.
Generate the document and send it in the same Flow.
Pair merge fields with the send action and the agreement builds itself on the way out. Your Flow reads the record, fills the template, and hands the finished document to the signer with nothing left blank.
- Merge tokens anywhereStandard fields, custom fields and related record values, all resolved on send.
- Locked layoutSignature and date positions stay where your template put them, every time.
- Roles decide the fieldsEach signer only sees the fields their role owns.
- Values come backWhat the signer typed writes into the fields you mapped.
Questions admins ask about Flow
Can I send a document for signature from a Salesforce Flow?
Yes. SignSecure ships Flow actions, so a record-triggered or scheduled flow can send a signature request with no code. Admins configure the template, recipients and mapped fields inside Flow Builder itself.
Build your first signature Flow this afternoon.
Free to start, no card needed. Flow actions are included on every paid plan.