We’re excited to share that the BoldSign eSignature integrations are now available on Zapier. You can connect BoldSign with over 5,000 external applications on Zapier, streamlining the eSignature process by enabling you to automate document workflows based on the document sent, declined and completed, and send signature request.
Whether you’re an HR professional, relators, healthcare providers, financial institution, law firms, or someone looking to streamline document workflows, this blog post is for you. In this post, we’ll show you how to integrate BoldSign with Zapier and automate your document workflows efficiently.
Automating routine manual work can save a significant amount of time, increase productivity, and eliminate manual errors. For instance, let’s say you are an HR manager responsible for the new employee on-boarding process. Typically, you would receive new hire data via Google Forms and manually create and send the eSignature document based on that data. Once the agreement is signed, you would need to download the document and upload it to your company’s Google Drive. Let’s see how to automate this process on Zapier.
When it comes to automation, triggers and actions are the key building blocks in Zapier. Triggers are events that cause an action to occur, while actions are the operations performed on an app when the trigger condition is satisfied.
BoldSign offers a range of triggers and actions in Zapier that can help you automate your eSignature workflows with ease. Here’s what you need to know about BoldSign’s supported triggers and actions:
With these triggers, you can automate actions on other connected apps. For example, you could automatically upload a document in Google Drive when a document is completed in BoldSign or update a Google Sheets with newly sent signature request details.
To perform this action, you need to provide the following information:
With this action, you can create and send new signature requests automatically when a trigger event occurs in a connected app. For example, you could create a new signature request in BoldSign whenever a new entry is made in Typeform or when a particular Pipedrive deal reaches a specific stage.
Zaps can be created in Zapier either from existing templates or from scratch. We have included several templates for popular integrations on the BoldSign Zapier integration page to make it easier for you to get started. You can start creating a Zap using one of these templates, or you can create a Zap from scratch if your use case is not covered by the existing templates.
In this blog post, we will create Zaps in Zapier to automate the previously discussed HR manager scenario. Here’s an overview of the process flow and the apps that will be used:
To make this process easier to understand, look at the below flowchart that demonstrates the workflow.
We should create two Zaps for our scenario. Before moving into Zap creations, assume that you have created a form in Google Forms with required fields and share it to the new employee named “Alex Gayle”. He has filled in the form and submitted the response.
To automate the process of creating a new signature request in BoldSign, we need to create a Zap in Zapier that triggers when a new response is submitted in Google Forms.
However, before creating a Zap for this, we should have a BoldSign document template. Because the BoldSign action in the Zap requires a template to send the document for signature. You can create a new template in the BoldSign web application or use an existing one. If you’re not familiar with BoldSign templates, check out the linked article.
Now, let’s create a Zap in Zapier for connecting these two apps.
Now, let’s assume that the new engineer “Alex Gayle” has signed the signature request successfully and the document is now marked as completed.
Next, we have to upload the completed document to Google Drive. Automatically uploading completed BoldSign signature request documents to Google Drive provides a convenient way to store completed documents safely in the cloud and access them whenever needed. By setting up this automation, manual document transfers are no longer necessary. Let’s create a Zap in Zapier for connecting this.
The required Zaps are created for our scenario. You can view the created Zaps on the Zaps page in Zapier.
Now we have successfully automated the employee on-boarding agreement process, which means that from now on, when a new employee joins the company, there will be no need for manual efforts to complete the on-boarding agreement process. These automations, created in Zapier, save a significant amount of time and eliminate the possibility of human errors, making the process more efficient and reliable.