How to Pass Signatures from Apps to Doc Gen in Noca
Pass signatures from Apps to Doc Gen in Noca
Turn a signed form into a finished PDF, mapped field by field
You collect details and a signature in a form, and you want all of it on a real document you can send to Salesforce, drop in Google Drive, or hand off anywhere else. This guide does exactly that. We build a one-page form that asks for personal details and a signature, map every field to a Word template, and let a flow fill the template and output a signed PDF. The example here is a simple registration form. When someone signs and clicks Proceed to Confirm, the flow builds the PDF and drops it into Slack. The whole thing took a couple of minutes to build.
Watch & Learn
Follow these steps to pass form fields and a signature into a PDF:
Steps:
1
Start with a prompt to build the form
- Prompt Noca to create your app, for example: create an app with a one-page form that asks for personal details and then a signature, and the submit button should say proceed to confirm
- You get a simple form that collects the details and captures a signature on a canvas
2
Add an on-click event to the submit button
- Open Events in the App Builder
- Under On Click Proceed to Confirm, attach the flow that will push the data to your document
- If you also want to pull data in when the page loads, add an On Load action instead
3
Open your template in Word and launch the Noca add-in
- Open the Word document you want to fill
- Click Open Noca AI to launch the add-in inside Word
4
Add and name your text inputs
- In the add-in, go to Inputs and click Add Input
- Click where you want the field in the document, choose the Text field type, insert it, and give it a name so you know what it is (first, last, and so on)
- Repeat for each text field you want to map
-
5
Add a signature input
- Add another input where the signature belongs
- Set the field type to Signature and insert it, then name it (signature 1 in this example)
6
Save your mapped template
- Once every field is mapped, save the document
- Your template is ready, with a placeholder for each input including the signature
7
Open your flow in Noca
- Back in Noca, open the flow tied to your form
- The first node is your Form With Signature node, mapped automatically from the form
8
Drop your template into the Word node
- The second node is the Word node
- Upload the template you just saved, and Noca reads the input fields you named
-
9
Map the template fields to your form inputs
- For each field the template found (signature 1, first, last), open your output App Fields
- Go to the personal details form, then Inputs, and drag each form field onto its matching template field
10
Choose the fill mode and output type
- Set the fill mode to Auto fill, or use User Interaction if you want a step in between
- Set the output format to PDF Document
-
11
Set the link limits (optional)
- Review the URL expiration, set here to 7 days
- Set the sign access mode, public in this example, and change it to private if you want to restrict access
12
Add a delivery step
- Add a node to decide where the PDF goes
- This example uses Slack to send a notification with the document, but you can push it to Salesforce, Google Drive, or anywhere else
13
Make the flow live
- Check that the flow is live
- If it is not, click Go Live
14
Save to commit the flow
- Go back to your form and click Save
- This commits the flow to your project
15
Preview and fill out the form
- Open the preview of your site and run it
- Fill in the details, draw a signature, and click Proceed to Confirm
16
See your finished PDF
- The flow generates the document and delivers it to your chosen destination
- Here is the finished PDF in Slack, with all the details and the signature, just like the form collected them
Back to top