SIGN BUTLER V2 – Add Approvers, Signers, Receivers and Fillers via Flow

4 min read

If you need more control, more complex logic on how to select your signers then you can best setup a flow that defines the Signers.
You can write the logic that is required to fetch your signers and order them as required.

Approver #

Adding an Approver via Flow can be done by structuring the information in the following way:

Note: Approvers should be ordered before signers.

The information parts are separated by a pipe symbol “|”, and lists of information are separated by a semi-colon “;”

Here an overview of all information

type: Required. signer or receiver or approver
signing methods: Should be empty as approver does not need to sign the document.
approver Id: Required. Id of a User, Lead or Contact record. Any other Id will also work if you are not sending from a User/Lead/Contact but it has to be a valid Id
FirstName: Required
LastName: Required
Email: Required
Locale: Optional. Leave empty when taking the locale of the current User
Order: Optional. Leave empty for auto-numbering in the order of the supplied signers to the list
SubOrder: Optional.

SIGNER #

The information parts are separated by a pipe symbol “|”, and lists of information are separated by a semi-colon “;”

Here an overview of all information

type: Required. signer or receiver
signing methods: Required. “;” split list of signing methods like Scribble, Handwritten, MailOtp, Upload
signer Id: Required. Id of a User, Lead or Contact record. Any other Id will also work if you are not sending from a User/Lead/Contact but it has to be a valid Id
FirstName: Required
LastName: Required
Email: Required
Locale: Optional. Leave empty when taking the locale of the current User
Order: Optional. Leave empty for auto-numbering in the order of the supplied signers to the list
SubOrder: Optional. for Parallel signing. Signers can have the same Order but should have a different sub Order in Parallel signing. Leave empty if no Parallel signing is required
Form fields for signer: Optional. if using Form Fields, which ones are for the current signer. Supply a “;” separated list of MergeFields for the Form Field. Leave empty if all Form Fields are for the first signer
Documents to attach: Optional. If the signer must upload documents, provide the list here. each document must have following information that is split by a colon “:”
– Name of the document
– Required or Optional

RECEIVER #

Here an overview of all information

type: Required. signer or receiver
signing methods: Should be empty as receiver just need an update on the statis of the sign request.
receiver Id: Required. Id of a User, Lead or Contact record. Any other Id will also work if you are not sending from a User/Lead/Contact but it has to be a valid Id
FirstName: Required
LastName: Required
Email: Required
Locale: Optional. Leave empty when taking the locale of the current User
List of actions that trigger a mail to the receiver: Required. REQUEST_CREATED;REQUEST_SIGNED;REQUEST_COMPLETED

FILLER #

The information parts are separated by a pipe symbol “|”, and lists of information are separated by a semi-colon “;”

Here an overview of all information

type: Required. => filler
signing methods: Required. This will be ignored. Just put “NA”
filler Id: Required. Id of a User, Lead or Contact record. Any other Id will also work if you are not sending from a User/Lead/Contact but it has to be a valid Id
FirstName: Required
LastName: Required
Email: Required
Locale: Optional. Leave empty when taking the locale of the current User