Zapier allows you to integrate your application with Documint in just a few clicks.
The next few articles will walk you through the steps necessary to set up your integration using Zapier.
Below is the workflow (Zap) we will create with Zapier.
We will use Google Forms as our data source for this example. In your case, you will probably connect to a CRM-like application (ie. Salesforce.com or HubSpot).
This, of course, is what we’ll use to automate our document creation.
We will use Google Drive as our document storage application. In your case, you may want to attach the document with the original record in your application or send it via email.
Before we get started it’s important to understand what Zapier is and its role in the process. Zapier describes themselves as being “the glue that connects thousands of web apps.” Zapier allows you to connect your applications, such as Salesforce, HubSpot, MailChimp to thousands of other applications (including Documint) without writing a single line of code!
Check out Zapier’s full list of applications to see if your application is supported.
Zapier describes a Zap as:
an automated workflow that connects your apps and services together. Each Zap consists of a trigger and one or more actions. When you turn your Zap on, it will run the action steps every time the trigger event occurs.
source Zapier Documentation
In other words, a Zap is simply a connection from one application to one or more applications. In our case, we are going to create a Zap that connects Google Forms, Documint, and Google Drive.
Our Zap (workflow) will go something like this…
When a new entry is submitted to our Google Form (this is the “trigger” event in Zapier’s terms)
Send the entry data to Documint and merge it with the template we specify (this is an “action” in Zapier’s terms)
Then take the document that was created by Documint and store it in the folder we specified in Google Drive (this is another “action” in our Zap)
To follow along with this guide you will need the following: