signNow delivery
The signNow delivery sends generated documents to signNow for electronic signing. Before configuring the delivery, connect your signNow account by clicking App settings:
Note
The full process of generating a document and signing it with signNow is described in this blog post.
Connect to signNow
After clicking the App settings button, you need to enter the Client ID and Client secret.
Note
signNow delivery requires an active signNow API plan. Please check out the article to find out how to obtain the Client ID and Client secret values.
Then grant Plumsail access to your signNow account.
Once connected, configure the signNow delivery settings.
Main settings
Specify the email subject and body. See how to use tokens inside these fields.
Add as many recipients as needed and assign roles to them. You can add them manually or dynamically using tokens. Check how to specify recipients dynamically based on your data.
Advanced settings
Expand the Advanced section to configure more settings:
Enable Sequential signing to control the signing order. Drag and drop recipients to define the sequence in which they sign the document:
You can also configure an expiration period for envelopes and set up reminder notifications. By default, envelopes expire after 30 days. After that, recipients can no longer view or sign them. When reminders are enabled, specify how often notifications are sent. Make sure the reminder frequency is shorter than the expiration period.
Important
Your document template must have signNow text tags to be successfully sent to signNow for signing.
Use custom signNow tags
SignNow text tags are special combinations of symbols that preset the location, type, size, and other settings of such fields as Signature, Initials, Date, and more.
You need to add signNow text tags to the document template before uploading the document to signNow, which means before starting the process that triggers the signNow delivery.
Below are some common examples of text tags:
{t:s;r:y;o:"Signer1";}- a text tag for a required signature field.{t:t;r:y;o:"Signer1";l:"Date";}- a text tag for a required date field.
Both are for the signer having the role ‘Signer1’. This is how the tags will appear for the signer:
The tags contain the following parameters:
Tag |
Represents |
Parameters |
|---|---|---|
t |
Type |
|
r |
Required |
|
o |
Role |
|
l |
Label |
|
Important
signNow text tags should have roles and this role must be exactly the same as you indicated in the signNow delivery.
Additional parameters:
Tag |
Represents |
Parameters |
Description |
|---|---|---|---|
t |
TYPE of the field |
s (for signature) i (for initials) t (for text) d (for dropdown) c (for checkboxes) |
For every field |
r |
REQUIRED |
y (for required) n (for optional) |
For every field |
o |
ROLE |
“ “ |
For every field |
l |
LABEL |
“ “ |
For every field |
dd |
DROPDOWN |
“option1, option2, option2, ….” |
Only for Drop down fields |
f |
FILE |
“ “.pdf” |
File attachment |
w |
WIDTH |
w (width) |
For every field |
h |
HEIGHT |
h (height) |
For every field |
v |
VALIDATOR_ID |
v (validator_id) |
Only for Text field |
Note
We recommend you enclose signNow text tags in single curly brackets - { } - instead of double ones to avoid any conflicts with Plumsail Documents tokens.
See the signNow documentation article for more details and examples.
Specify recipients dynamically based on your data
You can define recipients dynamically using tokens in the Name and Email fields. The data passed to the process determines who receives the document.
The Email field can contain a single address or a list of addresses separated by commas or semicolons:
{
"email": "Derek Clark <d.clark@contoso.com>; Jessica Adams <j.adams@contoso.com>"
}
If you provide a list of recipients in the Email field, the Name field is ignored.
You can specify recipient names in the list by placing names before the email address:
Behavior details:
If no name is provided, the email address is used as the recipient name.
If Sequential signing is enabled, recipients receive the document in the order specified in the list.
If you add an Access code, all recipients in the list receive the same code. To assign different codes, add recipients individually in the Recipients section.
Use tokens inside email subject and body
You can insert values from your data using tokens.
Click { } to open the list of available tokens.
For example, if your data contains a property called address, insert it using the token {{address}}.
Tokens work the same way as in document templates and also support value functions.
You can also use predefined tokens:
{{@date}}- the current date and time{{@number}}- the current document number.
Note