- Home
- Resources
- Integrations
- Filevine
Filevine Zapier integrationAutomate Filevine with Zapier.
Filevine Zapier integration: 1 trigger, 10 actions and 9 searches to move case data in and out of Filevine without retyping it. Below, what each operation does for your firm, what it costs you, and where it trips people up.
Verified Trustpilot reviews · AI, automation & growth agency
What the Filevine Zapier integration actually does for a firm
Filevine is case management software built for law firms. Zapier links it to the rest of your tools through Zaps: small automations where one event starts a chain of steps. On Filevine's side you get one event to listen for, ten things Zapier can write, and nine ways to look up what already exists.
Three results come up again and again. First, a new matter opened without double entry: Find Contact spots the client, Create Project opens the file. Second, case data kept in sync: Update Project and Update Collection Item rewrite fields when something changes elsewhere. Third, data carried from one project to another with the Copy Data From and Copy Data To pair, so a related matter starts with what the first one already knows.
Now the limits, because they matter just as much. Filevine exposes a single trigger, New Event, so every Zap that starts in Filevine starts there. There is no action to delete anything, and no way to upload a document: Find Document only looks one up by its ID. If you need a call the list does not cover, API Request (Beta) is the escape hatch, but it is a technical one.
Comparing tools before you commit? Our Make vs Zapier breakdown sets the criteria side by side, and the Zapier review covers the platform itself.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here they are in plain English.
- Zap
- The automation you build: one starting event, then one or more steps that run every time that event happens.
- Trigger
- The event that starts the Zap. Once the Zap is switched on, Zapier waits for it and nothing runs before it shows up.
- Action
- What the Zap does after it starts: the step that writes, creates or changes something in Filevine or another app for you.
- Task
- What Zapier bills you for: one action that went through. Your plan's allowance is a count of those, nothing else.
- Polling vs instant
- Polling means Zapier checks the app on a timer. Instant means the app calls Zapier itself the moment the event happens.
- Filter
- A step that lets the Zap carry on only when what arrived matches your condition, and stops it quietly otherwise.
- Search step
- A step that looks up something already in an app, like a contact or a project, so the next steps can use it.
What a Filevine Zap really costs
Filevine is not a premium app, so it runs on the free plan. The bill depends on actions, not on how often Filevine sends events.
- Free plan100 tasks per month, unlimited Zaps
- Zap length on free2 steps: one trigger, one action
- Trigger cost0 tasks
- Filevine app tierNot premium, available on free
The New Event trigger never costs a task. Each action that succeeds counts as one, and an action that fails is not counted. The catch on the free plan: a Zap stops at two steps, one trigger and one action. Add a second action, a filter or a search step and it becomes a multi-step Zap, which needs a paid plan. Since most useful Filevine Zaps start with a search (find the project, then update it), plan for that early.
Connect Filevine to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Filevine account, plus access to any project you do not own yourself but want the Zap to read or change.
- 02
Pick Filevine
Type Filevine in the search box of the dialog, select it in the results, then click Add connection. A new browser tab opens on Filevine's own sign-in screen.
- 03
Sign in and grant access
Log in with your Filevine credentials and allow Zapier to use the account. From then on, every Filevine step in every one of your Zaps reuses this single connection.
Your first Zap: open a project for an existing client
GoalWhen a chosen Filevine event comes in, find the related contact and open a new project for them.
- 01
Build: start with New Event
Click to create a Zap, choose Filevine as the app and New Event as the trigger. In the required Event field, pick the Filevine event you want to react to.
- 02
Test the trigger
Run the test. Zapier pulls the three most recent matching items from your account, so you map fields against a real one instead of guessing.
- 03
Add Find Contact
Add Find Contact, choose which contact field to search by, and map the value from the trigger. This search makes the Zap multi-step, so a paid plan is needed.
- 04
Add Create Project
Add Create Project. Set the Project Type, then map the contact the search found into the Contact field. Both are required.
- 05
Test, then Publish
Test each step and read what came back in Filevine. When the new project looks right, click Publish to switch the Zap on.
The Filevine trigger
1 event starts a Zap when something happens in Filevine, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Event
Instant triggerIn Zapier“Triggers on a new event.”
This is the only door into Filevine: the Zap starts whenever the type of Filevine event you selected takes place, and hands its data to the next steps. Every Filevine-driven automation you build begins here, whatever it does afterwards.
Filevine actions
Filevine gives you 10 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Collection Item
ActionIn Zapier“Creates a new collection item.”
Adds a new item to a collection inside a project, leaving the items already there untouched.
Create Contact
ActionIn Zapier“Creates a new contact.”
Adds a person or organization to your Filevine contacts, ready to be linked to matters.
Copy Data From
ActionIn Zapier“Creates a reference to data in a project. This action supplies the data output to a "Copy Data To" action, which should be included in your Zap as a subsequent step.”
Grabs a reference to data inside one project, without writing anything yet. On its own it does nothing visible: it prepares a handoff.
Copy Data To
ActionIn Zapier“Copies data from a reference to a project. This action depends on the data output from a "Copy Data From" action, which should be included in your Zap as a prior step.”
Writes the data grabbed by Copy Data From into a target project, completing the pair.
Update Form
ActionIn Zapier“Updates an existing form.”
Fills in or changes values on a form that already sits inside a project. Despite what you might expect, it does not create a new form.
Create Project
ActionIn Zapier“Creates a new project.”
Opens a brand-new project in Filevine, which is how a matter starts life there.
Toggle Section
ActionIn Zapier“Toggles a project section's visibility.”
Changes whether one section of a project is visible, so the file shows the parts that matter at that stage.
Update Collection Item
ActionIn Zapier“Updates an existing collection item.”
Changes one existing entry in a project's collection instead of adding a new one.
Update Project
ActionIn Zapier“Updates an existing project.”
Rewrites fields on a project that already exists, so the file stays current without a manual edit.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
An advanced step that sends a raw request to Filevine using the connection you already set up, for anything the other actions do not cover.
Filevine searches
9 search steps look for data that already exists in Filevine, so a later step can use it.
A search step finds something that already exists in Filevine and passes it to the next steps. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not clean.
Find Collection Item
SearchFind or createIn Zapier“Finds a collection item by searching on item id.”
Looks up an entry inside a project's collection by its item ID and returns it to the Zap.
Find Contact
SearchFind or createIn Zapier“Finds a contact by searching.”
Checks whether a person is already in your Filevine contacts, searching on the contact field you choose.
Find Document
SearchIn Zapier“Finds a document by searching.”
Retrieves a Filevine document so later steps can use its details.
Find Form
SearchIn Zapier“Finds a form by searching.”
Locates a form by its name within a given project type.
Find Form by Selector
SearchIn Zapier“Finds a form by searching by selector name.”
A sibling of Find Form that searches by section selector name instead of the form name.
Find User
SearchIn Zapier“Finds a user by searching.”
Finds a member of your Filevine team so a later step can use that person.
Find Phase
SearchIn Zapier“Finds a phase by searching.”
Looks up a Filevine phase so a later step can reuse its exact reference.
Find Project
SearchFind or createIn Zapier“Finds a project by searching.”
Finds an existing matter by the project field you choose and returns it.
Find Project Type
SearchIn Zapier“Finds a project type by searching.”
Returns a project type, searched on the field you pick, so later steps can reuse it.
The three settings every search exposes
- Successful if no search results are found?Left on default, a search that finds nothing stops the Zap there and the dependent steps are skipped. Switch it on and the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this turns the search into a find-or-create: it asks for the fields needed to create the missing item, and the setting above disappears.
- If multiple search results are found?Keep the first match (the default), stop the Zap, or pass every match along at once.
When a Filevine Zap breaks
Zapier publishes no Filevine-specific help article, so the known failure points are the ones every Zap shares.
None of them shows up during the first test. They appear later, once real cases are flowing. If one bites, our Zapier troubleshooting guide walks through the fixes.
No catch-up on old cases
A Zap only reacts to what happens after you publish it. Projects and events already in Filevine are ignored; moving that backlog is a separate job.A Zap that triggers itself
If an action writes something that produces the very event your New Event trigger listens to, the Zap sets itself off again and again and burns tasks fast.Bulk imports get held back
After a migration or a big import, a sudden flood of events can be held back by Zapier's flood protection instead of running one by one.Copy Data To alone fails
Copy Data To has nothing to write unless a Copy Data From step sits earlier in the same Zap. Build the pair, test both, and count two tasks per run.
Need help automating Filevine with Zapier?
A person reads every message.



