How to send a document for signature with SignNow

With document templates set up in your SignNow account, you can build flows to automatically generate documents and send them out for necessary signatures. When you need a document signed, use the SignNow Send Document for Signature steptype to handle it.

Title

The title appears up top in Sidekick when your team reaches this step in the flow. We recommend using this field to explain which documents are being sent out for signature and why.

Create Document - Run Automatically?

Check this box to automatically generate a new document using the Template ID from your SignNow instance. You'll likely want to hard code a value here

Template ID

Use this field to specify the document template needed to generate the new document to be sent out for signature.

To find your template's document ID, open the document in SignNow and copy the section of the URL that appears after the last / forward slash character in the address.

For example, with the SignNow document open in your browser, the URL will look like this:

https://app.signnow.com/webapp/document/2dc757b4bd00d3e2913ce0924af027984012de4e

In this case, the needed document ID would be:

2dc757b4bd00d3e2913ce0924af027984012de4e

Invite Signer - Run Automatically?

Check this box to immediately trigger an email to a specified signer requesting their signature. For this to work, you'll need to use a variable in this steptype to pull in the customer's email address from your CRM automatically.

To Email

The email address to where the request for signature will be sent. Use the ➕ button to pull in the customer's email address from your CRM, or any other system connected to FlowEQ.

From Email

The email address from where your request for signature will be sent. You'll likely want to hard code a value for this field in this steptype.

Subject

The subject line as it will appear to the signature request recipient. You can hard code a value here, leave it for your team to fill out, or build a template using the ➕ variable button to populate the subject line with details from your FlowEQ-connected systems.

Message

The body of the email message which will accompany the signature request. We recommend using this field to explain whose signature is being requested and why. Similar to the subject field, you can hard code a value here, leave it blank for your team to fill out, build a template using ➕ variables to pull in data from your systems, or some combination of the three.

Hide Field in Sidekick? checkboxes

For each of the four fields above, you can check the Hide Field in Sidekick? box to prevent your team from seeing or changing these values in those fields before the signature request is emailed out.

If some of these fields have values hard coded values or populated using variables that will never need to be changed, you can use these boxes to give your team fewer fields to deal with in Sidekick.