Connect Zapier to Filevine (Using PATs)

🔄 Works with v2 of the Filevine API and the new Filevine-Zapier Connector version >= 3.1.

Once you've finished setting up Filevine and generating your Personal Access Token (PAT) for use with Zapier, follow this article to connect to Filevine from Zapier using PAT authentication.  If you have not already done so, please see the article titled: "Setup Filevine and Create a PAT For Zapier" when connecting to Filevine from Zapier for the first time.
 

ℹ️ Note: The new version of the Filevine-Zapier Connector (v3.x) that supports PATs was recently made available in Zapier, and the old version of the Filevine connector (v2.4.4 and v2.4.6) was deprecated and disabled on: 12/3/2025. If you have existing Zaps that use Filevine and you have not already upgraded them to use a PAT, then they are currently deactivated. Please see the following article to: "Upgrade from Using API Keys to PATs in Filevine-Zapier".

🔌 Connect Filevine to Zapier

1. If you haven't already done so, please follow the steps in this article to: "Setup Filevine and Create a PAT For Zapier".
2. Log in to your Zapier account.
3. Create a new Zap, and click on Trigger or Action in the workflow to begin connecting to Filevine. If you are modifying an existing Zap instead, open/duplicate an existing one where you want to add Filevine, and add a new step to the Zap by (or click an existing step/trigger to replace it by clicking the "Change" button in the App field for the step).
   
   
   Figure 1. Create a new step by clicking Trigger or Action, or modify an existing step by clicking Change next to the App name.
    

4. When the “Choose App” dialog appears, search for "Filevine", and select Filevine from the list.
    

   

   Figure 2. Choosing the Filevine connector app in Zapier.
    

5. Within the new Filevine step details pane, look for the the “Account” field (shown boxed in red in Figure 3 below) under the Setup tab, and click on "Select an account" or on the "Select" button. Or if you are modifying an existing step, click the "Change" button if an account is already listed.
   
   

   Figure 3. Click on "Select an account" or the "Select" button to choose or add an account.
    

6. If you don’t already have a PAT-based Filevine connection (named like: "Org: #"), click “+ Connect a new account” (see Figure 4 below), or choose an existing PAT-based connection and skip the following steps in this article.
   
   
   Figure 4. Click on "+ Connect a new account" to create a new Filevine connection.
    
7. In the window that appears titled “Allow Zapier to access your Filevine Account?” (See Figure 5 below), enter the following:
   • Personal Access Token: Paste in your PAT that you generated in Filevine in the previous help center article.
   • 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 an Account with a PAT for the Filevine-Zapier connector
    
8. Once you've entered your PAT and Org ID, click: “Yes, Continue to Filevine”.
9. If the token is valid, the dialog will close automatically without any error messages.

✅ You’re all set! Your Zapier account is now authorized to access your Filevine tenant securely using the service account and PAT, and the connection can be reused for other Filevine steps. You can now proceed with building out your automation.
 

ℹ️ 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".
   
    
   Figure 6. Open "Filevine Settings" in Filevine.
    
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).
   
   
   Figure 7. "Basic Info" tab in Filevine Settings > Orgs menu, showing the Org ID boxed in red.

🪲 Potential Bugs & Workarounds

1. "Invalid Request Error" or "Zap Could Not Be Switched On"
   If you are seeing an error when trying to turn on your Zap, this issue could be related to a bug where "API Key Manager" permissions are required to use the /subscriptions endpoint in Filevine.
   
   We are tracking this bug and are actively pursuing a fix with the Filevine development team. Here is a temporary workaround that may help resolve the issue:

   1. While logged into your Filevine account as an Account Admin, click your user icon (your initials) in the top-right corner.

   2. Select Filevine Settings.
    

   3. From the left-side menu, click Orgs, and then choose the Advanced Access tab.
    

   4. Within the Advanced Access > Individual Access tab, click on the search box beneath Select a Member*, and search for your Zapier integration service account (typically: Zapier Service Account (zapier@filevine-cpi-service-accounts.com)).

   5. From the list of permissions, turn on the "Api Key Manager" permission by clicking on the toggle switch.

   6. Click "Save" in the bottom right hand corner, and try turning on your Zap again.
   
    

2. "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.