Upgrade/Migrate Filevine from a Legacy Version (API Keys) To Using PATs in Zapier

Use this guide to upgrade your current Filevine-Zapier connection (v2.4.4 or v2.4.6) that uses the legacy method of authenticating via API keys to the new version of the Filevine API that uses a Service Account and a Personal Access Token (PAT).  

If you are not sure whether your Zapier account is using the legacy version of the Filevine-Zapier connector or not, please see this article: How to check if my Filevine Org is currently using Zapier, and whether it needs to be upgraded to PATs

If you have trouble following the steps outlined in this article and need additional help getting connected to Filevine in Zapier with PATs, please contact Vineskills support: support@vineskills.com 
 

📌 Note: The new version of the Filevine-Zapier Connector (v3.x) that supports PATs was recently made public as of August 1st, 2025, and the old version of the connector (v2.4.4 and v2.4.6) will be deprecated and made unavailable on December 2nd, 2025. Please follow this article to upgrade all of your Zaps as soon as possible to avoid interruption to your Zapier automations.

⚠️ Note: All Filevine v2.x connector steps in your existing Zaps must be manually upgraded/migrated to the latest version because Zapier considers the authentication method change (API keys to PATs) to be a "breaking change". Your Zap steps cannot be automatically upgraded from v2.x to v3.x in a batch. However, once you're using PATs, all future updates will be automatic. Please repeat steps 1 through 5 in this article on all of your Filevine Zap steps.

⬆️ How to Upgrade/Migrate Your Existing Zaps to Use PATs

1. If you haven't already done so, please follow the steps in this article to: "Setup Filevine and Create a PAT For Zapier", and be sure to save your PAT somewhere secure.
2. Log in to your Zapier account.
3. Open/duplicate an existing Zap that you would like to upgrade and uses the old version of the connector which authenticates with API keys (v2.4.4 or v2.4.6).
4. Find and click on an existing Filevine action/trigger within the Zap. In the step's details pane, click “Change” next to the old Filevine App name, e.g. "Filevine (2.4.6)" (See Figure 1 below).
   
   
   Figure 1. Changing an existing Filevine (2.4.6) action to use a newer connector version.
    
5. When the “Choose App” dialog appears, search for and select Filevine (see Figure 2 below) to choose the newest version.
   
   
   Figure 2. Choosing the newest version of the Filevine connector.
    
6. Within the step details pane, look for the the “Account” option under the Setup tab, and click on "Change" (see Figure 3 below).
   
   
   Figure 3. Click on the Change button to replace an outdated Filevine connection.
    
7. If you don’t already have a PAT-based Filevine connection (v3.1.0 or newer), click “+ Connect a new account” (see Figure 4 below), or choose an existing PAT-based connection and skip the rest of the steps in this article.
   
   
   Figure 4. Click on "+ Connect a new account" to create a new Filevine connection.
    
8. In the window that appears titled “Allow Zapier to access your Filevine Account?” (See Figure 5 below), enter the following:
   • Personal Access Token: Copy and paste your PAT.
   • Country: Choose either US or CA depending on what country you're connecting from.
   • Org ID: Find your Org ID in Filevine under: Filevine Settings > Orgs > [Org Name] > Basic Info, and look for the "ID" field. For more info on how to find your Filevine Org ID, please see the "How to Lookup your Filevine Org ID" section below.
   
   
   Figure 5. Connect to Filevine in Zapier using a PAT.
    
9. Once you've entered your PAT and Org ID, click: “Yes, Continue to Filevine”.
10. If the token is valid, the dialog will close automatically without any error messages.

✅ Your Zapier account is now authorized to access your Filevine tenant securely via PAT, and you can now proceed to update all existing Filevine steps to use the new connector version and PAT connection.

ℹ️ How to Lookup your Filevine Org ID

1. Log in to Filevine.
2. Click on your user initials/icon in the top-right corner.
3. Go to "Filevine Settings".
   
    
4. In the left-side menu, select Orgs.
5. Click on “Choose for an Org” dropdown and select the name of the organization you would like the Org ID for.
6. Under the Basic Info section, look for the ID field (directly above API Keys). Write down or copy your Org ID (boxed in red below).
   
   

🪲 Potential Bugs & Workarounds

1. "Invalid Client"
   If you are seeing an "Invalid Client" error when trying to connect to Filevine from Zapier with PATs, this is could be due to either an invalid or incorrect PAT, the PAT not being connected to the Zapier service account, or the Zapier integration not being enabled in Filevine.
   
   Please confirm that you have followed all of the steps 1-3 outlined in the main article above and that you have completed the following:
   • Created the service account for Zapier
   • Enabled the Zapier integration
   • Associated your PAT with the Zapier service account upon creation 

If your issue persists, please reach out to support@vineskills.com and mention "Zapier" somewhere in your email. Let us know exactly the error you're seeing. Screenshots and loom videos are recommended.