Feathery Documents allow you to automatically fill, generate, and sign any document
Automate your document workflows with Feathery via Documents.

Video Demo

Below is a comprehensive video demo of Feathery Documents with detailed timestamps

Autofill a document template from forms

If you have an existing document template you want to automatically fill out and route, you can upload it to Feathery and map form fields and hidden fields from your forms to the documents. You can do this in one of two ways:
  1. 1.
    Feathery detects existing fillable fields in your document and allows you to map fields to them.
  2. 2.
    You may annotate the document with additional text and signature fields and position them however you want. The annotated fields may also be mapped to form/hidden fields.
To map fields, simply click the document/annotated field and use the right panel that appears to select the form or hidden field to map to the document field. You may also right click the document field and select "Attach Form Field". Once a document field is mapped it is shown with a green color.
Not all form fields can be mapped to all types of document fields. Feathery will enforce this and only offer form fields types for mapping that are compatible. Some field mappings require additional property inputs to complete the mapping. These extra properties will dynamically appear in the right panel when a document field is selected and mapped to a form field.
  • When mapping form field types that have options (dropdowns, checkbox and radio groups, button groups and question matrix) to either a document checkbox or document radio button field, you must select a field "Option Value" that will cause checkbox/radio to be checked at document fill time. In other words, if the mapped form field has this option selected, check the document checkbox or radio button.
  • When mapping a repeating form field to a document field, you may optionally enter a "Repeat Number" to indicate which repeating value to map. This is optional and if not supplied, then the list of values from the repeating form field is used to fill the document field (as appropriate).
  • When mapping a question matrix to a document checkbox or radio button, you must select a "Matrix Question" to be mapped as well as an "Option Value" (see above) . The question matrix contains multiple questions, but a mapping to a particular document checkbox or radio can only be for a particular question.
Once you've mapped your document, you can integrate it into your existing workflow for filling and routing to the desired location. For example, you can include your document in a custom email integration to be emailed to recipients.

Autogenerate a new document from forms

Feathery also allows generating new documents from scratch if you don't have an existing document template you want to fill out. Once you have a form you wish to export to a PDF, there are two ways to generate/export it.
  • Once users have completed the form you may go to the Results tab in the form editor and select submissions you wish to export. On the submission details screen, use the "Export to PDF' button to have the system export the form submission data to a PDF and email it to you. Do this for each submission you are interested in.
  • You may also choose to have the form PDF export mailed to some email addresses upon various events such as form completion, etc. Use the email integration found on the form editor's integrations tab to do this. Select the email integration and during setup check the "Attach PDF Export" checkbox and save it.
Feathery will automatically generate a PDF document that includes a page (or more) per step of the form and contains step names, field labels, and field values.

Sign a document directly

Feathery also supports a Docusign-like flow when you want to fill out your document directly without relying on a form intermediary.

Manually Request Signatures

You can manually invite users via email to sign documents or trigger signature flows directly to complete yourself.

Automatically fill and/or invite signers

You can automatically fill document templates based on form events. You can also optionally route the document out for signature / manual input afterwards.
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. If it has form fields mapped on it, the document will be prefilled with existing field values before being sent out.
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.