SignRequest

To use the SignRequest app, the user has to pay the API usage. For more information on pricing, see here.

The SignRequest modules allow you to monitor, create, update, send, retrieve, list, and delete the documents, document attachments, events, SignRequests, teams, and templates in your SignRequest account.

Getting Started with SignRequest

Prerequisites

A SignRequest account - create an account at signrequest.com/.

The module dialog fields that are displayed in bold (in the Integromat scenario, not in this documentation article) are mandatory!

Connecting SignRequest to Integromat

1. Go to Integromat and open the SignRequest module's Create a connection dialog.

2. In the Connection name field, enter a name for the connection.

3. In the Subdomain field, enter your account domain details. For example, if your account URL address is https://www.xyz.signrequest.com then your subdomain is xyz.

4. Click Continue.

5. Confirm the access by clicking Authorize.

The connection has been established.

SignRequests

List SignRequests

Retrieves all SignRequests.

Connection	Establish a connection to your SignRequest account.
Filter by Who Signs Document	Select or map the option to choose the users to filter the SignRequests: Only me Me and Others Only Others
Filter by Document Sender Email	Enter (map) the email address of the sender who is requesting the signature to list the requests that match the specified email address.
Limit	Set the maximum number of SignRequests Integromat should return during one execution cycle.

Get a SignRequests

Retrieves a SignRequest.

Connection	Establish a connection to your SignRequest account.
SignRequest ID	Select or map the SignRequest ID whose details you want to retrieve.

Create Quick SignRequests

Creates a document and SignRequests in one call.

Connection Establish a connection to your SignRequest account.

Document File Through

Select or map the document file through for which you want to create the SignRequest:

URL
Data
Template

File URL Enter (map) the URL address of the document for which you are creating the SignRequest.

Source File Enter the source file information for which you want to create the SignRequest:
File Data
Enter (map) the file data.
File Name
Enter (map) the file name.

Template Select or map the Template of the document for which you want to create the SignRequest.

Signers

Add the signer's details:

Email	Enter (map) the email address of the signer.
Authorization Role	Select or map the signer's applicable authorization role: Sign Sign in Person Approve Notify Copy
User Stamp For Approve Only	Select whether you want to place an approval stamp on a document when a signer approves the document.
Embed URL User ID	Enter (map) the embed URL address of the User ID. For more information, see In-Person Signing.
Signing Order	Enter (map) the signing order details of the document.
First Name	Enter (map) the signer's first name.
Last Name	Enter (map) the signer's last name.
Language	Enter (map) the document language.
Force Language	Select or map the language applicable to the signer.
Password	Enter (map) the signer's password.
Verify by Phone Number	Enter (map) the phone number used for the text message verification. A country code including the plus-sign is required.
Verify by Bank Account	Enter (map) the bank account used for the bank account verification.
Redirect URL	Enter (map) the redirect URL address to which the user should be redirected after completing the sign.
Redirect URL Declined	Enter (map) the redirect URL address to which the user should be redirected after declining the request.
Chained Document	Select or map the reference document that the signer should sign before signing this one. For more information, see the documentation. About the Chained Document (in Signers) The easiest way of working with the chained document is by sending the requests backward. Please see the following example: Context: You want to send three different documents to a customer. 1. Create three documents using the Create a Document module. 2. Create a SignRequest using the Create a SignRequest module with Document 3 URL address in the documents field and Document 2 URL address in the after_documents field in the signers' array. This will not trigger a SignRequest email to be sent to the signer. 3. You create a SignRequest using the Create a SignRequest module with Document 2 URL address in documents field and Document 1 URL address in the after_documents field in the signers' array. This will not trigger a SignRequest email to be sent to the signer. 4. You create a SignRequest using the Create a SignRequest module with Document 1 URL address in the documents field without providing any details in the after_documents field. Because this SignRequest has no after_documents email, it triggers a SignRequest email to be sent to the signer. Note: Resending the SignRequest email (in this case for Document 3 and Document 2) will trigger the SignRequest email to be sent to the signer even though there was none sent before. When `after_document` references a document where the signer in question already has signed or declined they will still receive a SignRequest email as we cannot redirect them anymore. It's only possible to reference documents that are not fully signed (or declined) yet.

Email Sender Enter (map) the sender's email address. Required when authenticated as a Team. The reply-to email address

Email Sender Name Enter (map) the sender's name who is sending the SignRequest.

Email Subject Enter (map) the email subject line.

Email Message Enter (map) the email message body.

Required Attachments Add the required attachments for the SignRequest.

Needs Preparing Select whether the sender of the SignRequest prepares the document before sending the request out.

Redirect URL

Enter (map) the URL address the user must redirect to when a document is signed.

This only works when there are no chained documents for this signer anymore.

Redirect URL Declined

Enter (map) the URL address the user must be redirected to when a document is declined.

This only works when there are no chained documents for this signer anymore.

Send Reminders Select whether you want to enable the SignRequest to automatically remind the signers to sign a document on days 3, 8, 13, and 18.

Text Message Verification Locked Select whether a text message verification is needed before the signer can see the document.

Document Name Enter (map) a document name that you want to send for the SignRequest.

Document External ID Enter (map) the document's External ID to access from the external systems.

Document Events Callback URL Enter (map) the document events callback URL address.

Document Prefill Tags

Add the tags for the document:

External ID	Enter (map) the External ID of the document that can be accessed from external systems.
Text	Enter (map) the tag text.
Checkbox Value	Select whether you want to provide a checkbox value for the tag.
Date Value	Enter (map) the date to add the date tag.

Document Auto Delete Days Enter (map) the number of days after which a finished document (signed/canceled/declined) will be automatically deleted.

Document Auto Expire Days Enter (map) the number of days after which a non-finished document will be automatically expired.

Force Signature Color

Enter (map) the specific color for the signature. For example, #0000ff.

This only works for the draw mode and does not affect the color-saved signatures.

Disable Text Select whether you want to disable adding text to the document being sent for SignRequest.

Disable Date Select whether you want to disable adding dates to the document being sent for SignRequest.

Disable Attachments Select whether you want to disable uploading or add attachments to the document being sent for SignRequest.

Disable Emails Select whether you want to disable all the SignRequest status emails and the email that contains the signed documents.

Disable Text Signatures Select whether you want to disable the usage of signatures generated by typing the text.

Disable Upload Signatures Select whether you want to disable the usage of uploaded signatures (images).

Disable Blockchain Proof Select whether you want to disable storing timestamp proof hashes in blockchain integrations.

Note: The endpoint might return an empty Document Name / External ID / File / File From URL / Event Callback URL/ File from SF / Auto Expire Days / Auto Delete Days (/ integration/integration_data) fields. But, if you retrieve the signrequest afterwards, they will no longer be empty.

Create a SignRequest

Creates a SignRequest.

Connection Establish a connection to your SignRequest account.

Document URL Select or map the Document URL address for which you want to create a SignRequest.

Signers

Add the signer details:

Email	Enter (map) the email address of the signer.
Authorization Role	Select or map the signer's applicable authorization role: Sign Sign in Person Approve Notify Copy
User Stamp For Approve Only	Select whether you want to place an approval stamp on a document when a signer approves the document.
Embed URL User ID	Enter (map) the embed URL address of the User ID. For more information, see In-Person Signing.
Signing Order	Enter (map) the signing order details of the document.
First Name	Enter (map) the signer's first name.
Last Name	Enter (map) the signer's last name.
Language	Enter (map) the document language.
Force Language	Select or map the language applicable to the signer.
Password	Enter (map) the signer's password.
Verify by Phone Number	Enter (map) the phone number used for the text message verification. A country code including the plus-sign is required.
Verify by Bank Account	Enter (map) the bank account used for the bank account verification. At present, it is only possible to verify bank accounts using iDEAL.
Redirect URL	Enter (map) the redirect URL address to which the user should be redirected after completing the sign.
Redirect URL Declined	Enter (map) the redirect URL address to which the user should be redirected after declining the request.
Chained Document	Select or map the reference document that the signer should sign before signing this one. For more information, see the documentation. The easiest way of working with the chained documents is by sending the requests backward. Please see the following example: Context: You want to send three different documents to a customer. 1. Create three documents using the Create a Document module. 2. Create a SignRequest using the Create a SignRequest module with Document 3 URL address in the documents field and Document 2 URL address in the after_documents field in the signers' array. This will not trigger a SignRequest email to be sent to the signer. 3. You create a SignRequest using the Create a SignRequest module with Document 2 URL address in documents field and Document 1 URL address in the after_documents field in the signers' array. This will not trigger a SignRequest email to be sent to the signer. 4. You create a SignRequest using the Create a SignRequest module with Document 1 URL address in the documents field without providing any details in the after_documents field. Because this SignRequest has no after_documents email, it triggers a SignRequest email to be sent to the signer. Note: Resending the SignRequest email (in this case for Document 3 and Document 2) will trigger the SignRequest email to be sent to the signer even though there was none sent before. When `after_document` references a document where the signer in question already has signed or declined they will still receive a SignRequest email as we cannot redirect them anymore. It's only possible to reference documents that are not fully signed (or declined) yet.

Email Sender Enter (map) the sender's email address. Required when authenticated as a Team. The reply-to email address.

Email Sender Name Enter (map) the sender's name who is sending the SignRequest.

Email Subject Enter (map) the email subject line.

Email Message Enter (map) the email message body. The message may contain the following HTML tags: a, abbr, acronym, b, blockquote, code, em, i, ul, li, ol, and strong.
Note: Ensure that when the text to HTML ratio is too high, the email may end up in spam filters. Custom styles on these tags are not allowed.

Required Attachments Add the required attachments for the SignRequest.

Needs Preparing Select whether the sender of the SignRequest prepares the document before sending the request out.

Redirect URL

Enter (map) the URL address the user must redirect to when a document is signed.

This only works when there are no chained documents for this signer anymore. The fields in the mappable parameters will apply in general but will be overwritten for the specific signer by the signer's Redirect URL and Redirect URL Declined if they are defined.