Process Street

Automating tasks in your daily business life can have a drastic impact on your productivity.  With a tool like Process Street you can setup task and workflows to keep your business on track.

Add Formstack Documents to your daily routine and you can automatically populate documents like contracts, letters, and more.  You’ll never have to copy and paste or search for a template again.

In this example, we’re going to show you how to automatically generate a contract when we check off a certain task in our Process Street workflow, then we’ll send the contract out for signature using HelloSign.

To get started, we’re going to setup the template for our contract using a Word document.  Inside Word, we’re going to enter our boilerplate contract information, then the spots that we want to insert our customer information, we’re going to use merge fields that look like {$FirstName}, {$LastName}, {$Address}, etc.

These merge fields can be named anything you’d like, but no spaces or special characters.

Here’s what our contract template looks like:

Since we’ll be collecting a signature via HelloSign, we need to add a signature tag to our document so that HelloSign knows where to place the signature.  This tag is just like any other text in our document and looks like:   [sig|req|signer1]

Once we have our template finished, we need to upload it to Formstack Documents.  From the Documents page in Formstack Documents, click the New Document button and enter a name.  On the next step, select Office Document as the document type and then pick the file from your computer.


After you upload your template, you’ll be taken to the Settings tab where you can modify various options like the type of file that is generated and the name of the file.  For this example, we’re going to choose PDF as the output and we’re going to include our customer’s name in the name of the PDF file.


Next, we’re going to setup the delivery of our document so that it is automatically sent over to HelloSign for signature.  From the Deliver tab, click the New Delivery button and select HelloSign from the list.  Once you enter your HelloSign API Key, you’ll need to select the merge fields for the signer’s name and email address.


After you have saved your HelloSign delivery, we are done with the setup process in Formstack Documents and we’re ready to setup the integration with our Process Street workflow.  To help with the integration, we’re going to use our friends over at Zapier.

Inside Zapier, we’re going to setup a New Zap.  For the Trigger, we’re going to choose Process Street as the app, then New Task Checked as the trigger.


After you have authenticated your Process Street, Zapier is going to load a list of your workflow templates in Process Street.  Go ahead and pick your workflow and choose the task that you want to trigger the merge.

Next, we’re going to setup the Action of our Zap.  For the App, choose Formstack Documents and then Create Document Merge as the action.


Once you authenticate your Formstack Documents account, Zapier is going to load a list of the documents in your Formstack Documents account.  Go ahead and select the contract that you just setup and Zapier will load a list of the merge fields in your template.

For each of the merge fields, you need to pick the corresponding fields from Process Street.  This tells Zapier how to send your data over to Formstack Documents so that it is populated in the correct spot on your template.

After you have matched up all of your merge fields, go ahead and save your Zap and turn it on.  We’re ready for a test!  Open up Process Street and check off your task.  This will trigger Zapier to send the data over to Formstack Documents and populate the contract.

Here’s what our contract looked like waiting for signature in HelloSign:

Congrats, you’re all finished!  You can now automatically populate all kinds of documents from your Process Street workflows.  Can you think of any other ways you can use Formstack Documents to simplify your paperwork process?

Was this article helpful?
1 out of 1 found this helpful



Please sign in to leave a comment.