Zapier for Vinesign

This article covers how to set up Zapier for Vinesign as well as the most common zaps.

• Set Up the Integration
• Send a Document
• Send a Template
• Other Actions

Set Up the Integration

Setting up the Zapier and Vinesign integration requires you to find Vinesign by Filevine in Zapier and then connect your account using your API key.

Find Vinesign by Filevine

In Zapier, on the home page, click Explore Apps. 

In the search bar, search Vinesign and select Vinesign by Filevine from the dropdown. Then, click to connect Vinesign by Filevine.

Sign in to Your Account

In the Account field, click Sign in.

You’ll be asked to enter the API key and secret and your base URL. 

The Vinesign API key and secret can be found in Vinesign, in the Settings section, under the API Keys V2 tab. If you don’t see the tab, you do not have permission to view it, and you must have a Vinesign Admin enable it for you.

Next to the key and the secret, click the copy button and then paste then into the corresponding fields in Zapier.

The base URL can also be found in the API Keys V2 tab. Click on the link to the documentation page in this tab. The base URL is the start of the url of the API documentation page (up to the first slash).

Enter the information and click Yes, Continue to Vinesign by Filevine. Once your Vinesign account has been connected, you can see it in your Vinesign trigger or action. Zapier will test the keys for you and let you know if they are valid, expired, etc.

Send a Document

The steps below give an overview of how to set up a zap that uses the Send Document action.

Set Up a Trigger

To send a document, you will first need a trigger. This trigger is typically a file being added or updated in your third party Zapier integration. 

Note: To send a document through the Vinesign Zapier integration, that document must be a .doc or .docx file and have embedded merge codes. Learn more about merge codes.

Add an Action

Once the trigger from your third party is set up, click to Add Step, select Vinesign by Filevine, and choose the Action Event. To send a document, select Send Document from the action event dropdown.

Configure the Action

In the Configure tab of the Send Document action, fill out the fields. Click on a field name to view more information about it.

You will need to get the list of recipient(s) from your third party integration via an additional action, or add them manually. Recipient data can be entered as line items for multiple recipients. To learn more about Zapier line items, read https://zapier.com/blog/formatter-line-item-automation/.

Vinesign will do its best to guess if you leave a field blank, but note that each recipient must have an email or phone number specified.

Test

After you have entered all of the data, you can Test the action to make sure it works. If it doesn’t work, you should get an error about the fields that have issues. Once those issues are fixed, the document should successfully send and your zap is ready for use.

Send a Template

Sending a template is very similar to sending a document, with a few notable exceptions. 

First, instead of providing a file with merge codes, provide a list of template IDs (up to 10). You can also provide custom field values for custom field merge codes that exist in the template, these can be provided for each recipient as line items.

Other Actions

Vinesign provides a number of other actions that you can utilize in your zaps.

• Find or List Documents: Triggers when a list of documents based on the input fields changes.
• Get Document: Gets a document by ID.
• Get Document Signed File Info: Gets info about a signed file including type, name, and ID.
• Document History: Gets info about the history of a document.
• Download Document: Downloads a document from an ID.
• Download File: Downloads a file associated with a document, given a document ID and file ID.
• Resend Document: Resends a document from an ID.
• Expire Document: Expires a document so that it can no longer be signed.
• Find or List Templates: Triggers when a list of templates based on the input fields changes.
• Get Template: Gets a template by ID.