Document Signature Workflows
Fill out and sign your documents directly.
Last updated
Fill out and sign your documents directly.
Last updated
Feathery supports a combination of autofilling document templates and manually signing / entering information into the document as well.
You can manually invite users via email to sign documents or sign them directly yourself.
You can automatically fill document templates based on user interactions with a Feathery form. You can also optionally route the document out for signature / manual input afterwards.
All form-initiated workflows will start by prefilling the document with any existing form submission data that has been mapped to fields in the document.
If you configure a button in your form with the Sign Document action, you'll be able to allow your form users to sign documents directly as part of the form flow.
In your form email integration, you can add a link to an Feathery document for your email recipient to sign by including {{FeatheryDocument:<DOCUMENT_ID>}}, where <DOCUMENT_ID> is the unique ID of the document to sign.
The document to sign will already be autofilled with data from the current submission based on the relevant field mappings.
You can set up a fill trigger for your document template when a field value is changed or a form submission is completed.
For example, you may want to route a contract out for signature once a form submission is approved. You can annotate the document with a signature field, then set the document trigger to be when the approval status field value is changed to Approved.
When a submission is approved, the document will automatically be sent out for signature.
You can add additional people to be notified of sign events (document viewed / signed) other than the sender and recipient. Navigate to the Settings tab of your document, then click on the Notifications sidebar entry.
From this page, you may specify a list of emails to receive email notifications of signature events. You can also specify a form or hidden field wrapped in double curly braces (e.g. {{FieldID}}), which will populate a dynamic email to notify if the signature workflow is associated with a form submission.
You may also specify a Slack incoming webhook, which will send notifications of signatures and daily reports of outstanding signature requests.
