Availability: Business and Enterprise plans
If you’re ready to do some coding to automate your workflow even more, consider pre-filling information for your recipients and capturing events from your form.
Skip to:
Note: At this time, we’re unable to provide support for pre-filing information and capturing events from forms.
Learn more about embedding your form on a website on our developers portal.
How to pre-populate information in your form
When you pre-fill information on your form, your clients will only need to sign the document. Here’s what you can pre-populate:
Recipients: Pre-fill data in the authorization form. Note that only role variables are supported.
Metadata: Set metadata for the document you’ll generate from the form.
Variables: Pre-populate values to variables in your forms. Other than the [Document.Value] variable, all types of variables (both predefined role variables and custom variables) are supported.
Fields: Pre-fill values in a text, checkbox, date, and dropdown field in your form.
Learn more about pre-filling information in a form.
Pre-fill values using a direct link
You can pre-fill recipient data, metadata, variables, and fields — without embedding your form — by adding necessary data as a URL parameter.
Learn more about pre-filling values in your form using a direct link.
How to capture events from your form
Capturing events from your form is an ideal way to gain more control over how your embedded form behaves.
You can subscribe to the following types of events:
Loaded: Allows you to capture events when the form is loaded and the user is asked to complete an authorization form (recipient names and email addresses).
Started: Allows you to capture events when a user enters contact details for recipients and selects Review document.
Completed: Allows you to capture events when a user has filled out assigned fields and completed the document by selecting Finish. If you’d like to redirect a customer to a specific page once a document has been signed, you can easily do this by providing a callback for a “completed” event, then redirecting the user.
Exception: Allows you to capture events when an error occurs while a recipient is attempting to complete a document.
Learn more about events.