---
title: SIGN BUTLER V2 – Add Approvers, Signers, Receivers and Fillers via Flow
description: 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…
url: "https://pdfbutler.com/academy/sign-butler-academy/sign-butler-v2/sign-butler-v2-add-signers-receivers-and-fillers-via-flow/"
updated: "2025-10-07"
category: SIGN BUTLER V2
---

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

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.

[https://www.youtube.com/watch?v=dauOCSBFim8](https://www.youtube.com/watch?v=dauOCSBFim8)

###### Approver

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

approver|LIST(SIGNMETHODS)|ID|FIRSTNAME|LASTNAME|EMAIL|LOCALE|Order|SubOrder

Note: Approvers should be ordered before signers.

approver|Signingmethods|00509000004rrBbAAI|Igor|Stuyver|mail@pdfbutler.com|en_US|1|1

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

Adding a Signer via Flow can be done by structuring the information in the following way: signer|Scribble;Handwritten|00509000004rrBfAAI|Igor|Stuyver|mail@pdfbutler.com|en_US|1|1|fld1;fld2;fld3|Id Card:Required;Driver License:Optional

or

signer|Scribble;Handwritten;Upload|00509000004rrBfAAI|Igor|Stuyver|igor.stuyver@pdfbutler.com|en_US||||||SIGN_REQUEST_NOTIFY;SIGN_REQUEST_SIGNED

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
- witness: Optional. requires a witness signer. Value must be left empty or true/false
- suppress email types: Optional. List of email types to suppress (no sending) for the signer. Supply a ";" separated list of values: SIGN_REQUEST_CREATED;SIGN_REQUEST_NOTIFY;SIGN_REQUEST_SIGNED

###### RECEIVER

A receiver is someone who want to be kept updated on the status of the SIGN Request. receiver|Signingmethods|00509000004rrBfAAI|Igor|Stuyver|mail@pdfbutler.com|en_US|
 REQUEST_CREATED;REQUEST_SIGNED;REQUEST_COMPLETED

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

Adding a Filler via Flow can be done by structuring the information in the following way: filler|NA|0030900000ADlDIAA1|Arthur|Song|mail;.filler@pdfbutler.eu|en_US

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