Skip to main content
AutoImporter
Tom Copeland avatar
Written by Tom Copeland
Updated over a week ago

AutoImporter is a tool to automatically import data into Filevine from any third-party source - another app, a vendor, or data provider - completely hands-free. If you had a data feed that arrives in a reliable format, you can import that data to create a new Filevine project, or, you can update an existing Filevine project. In this article, we'll explain how the tool works and provide a demonstration.

AutoImporter allow you to:

  • Create a new Filevine Project from a packet of data

    • All Client Info (no custom contact fields at this time)

    • All Project Info - Name, Phase, Incident Date, Incident Description, Hashtags

    • All Static and Collection Sections

      • Custom Fields for data, text, dropdown, boolean (yes/no), text area, number, and Person Link.

You will need some technical assistance to send your first set of test data for initial schema mapping to Filevine.

First, let's review the Technical Requirements, or, if you're eager to get started, scroll on down to our first Use Case.

Technical Requirements

AutoImporter relies on data being sent in JSON format. AutoImporter also requires the data to be structured in a predictable manner. AutoImporter relies on your ability to accurately map the JSON schema from the source data feed to Filevine, and the tool works only when that schema doesn't significantly change with each new packet of data sent. Since you will only be mapping the schema you want to import, you only need to ensure the minimum required fields by Filevine's API to be received:

  • If creating a new Filevine Project, you will need First Name, Last Name, Project Name.

  • If updating an existing Filevine Project, you will need to map either First and Last Name, Full Name, or Project Name.

In other words, these are the basic minimum requirements for AutoImporter to successfully process a packet of data for Filevine import.

How It Works: Getting Started

AutoImporter provides a dedicated, secure URL to which you can have data sent to. To get started, you'll create a listener URL (also sometimes called a "webhook"):

Next, we want to send a test data packet to the URL in JSON format. There's lots of ways to test this. If you are employing a partner or third-party vendor or provider to integrate data with Filevine, now would be the time you would want to simply provide that URL to your vendor and ask them to send some test JSON data to you!

If you'd like to test the tool directly, we've created a testing workspace powered by Postman for you to use. Start by reading the Overview section to learn how to use this testing tool. You will simply replace the empty URL with your Import URL, send the data packet, and move on to the next step.

Here's a loom video to show you the process of testing data with our Postman workspace.

How It Works: Mapping Data

The mapping configurations are mostly self-explanatory, but there are a few key pieces of information to understand when mapping data to Filevine:

You have two choices for mapping data to Filevine currently:

  • Create a new Filevine Project

  • Update an Existing Filevine Project

Both options allow you to:

  • Push in Client Data, including contact information

  • Push in Filevine Project information, including Project Phase, Incident Date, Incident Description

  • Create or Update data in Static Sections

  • For Collection Sections, currently the tool can only create new Collection items*

Collection Items can be tricky! Keep this in mind when working with Collection Items:

  • Currently, Collection Items cannot be updated. Given the difficult of matching data to the correct existing Collection Item, we do not have it on our roadmap to allow the update of an existing Collection Item with AutoImpoter. It's better to use the Collection Section Update Importer provided by VineMigrator for that work.

  • You can create any number of Collection Items in any given section

  • You can create any number of Collection Items in more than one section on any Import URL.

Let's take a look at what mapping our test data and pushing through our first test looks like for using AutoImporter to Create a New Filevine Project!

Here's a look at how to map and test AutoImporter data to update an Existing Filevine Project!

COMING SOON...

Use Case Example: Lawmatics Lead to Filevine Projects

Use Case Example: One Filevine Org to Another Filevine Org

Use Case Example: Lead Management Source

Did this answer your question?