# Filevine ## Overview The Filevine Connector in DBSync Cloud Workflow enables seamless integration between Filevine - a cloud-based case management and legal operations platform - and other enterprise systems such as CRM, billing, document management, and analytics platforms. This connector allows organizations to automate the flow of case data, synchronize records, and streamline legal operations between Filevine and external systems, eliminating manual data entry and helping maintain consistent and synchronized operational insight. ## Key Benefits **For Business Users:** * **Unified Case Data:** Share client, matter, and case information across legal operations, finance, and service systems to ensure everyone works from the same source of truth. * **Accelerates Onboarding:** Ensure new cases are instantly available to legal teams in Filevine, complete with required details and documents. * **Enables Advanced Reporting:** Standardize project creation and link related cases to run detailed reports on case types, durations, and outcomes. * **Improves Collaboration:** Provide real-time access to up-to-date case data, tasks, and deadlines for all team members. **For Technical Teams:** * **Secure Connectivity:** Connect using Filevine’s secure API with token-based authentication. * **Flexible Integration Capabilities:** Support reading, creating, and updating core Filevine entities as part of integration workflows. * **Workflow-Ready Architecture:** Enable event-driven or scheduled synchronization to automate business processes. * **Improved Operational Efficiency:** Remove the need for staff to manually re-enter case or client details and maintain data consistency across systems and minimize manual entry mistakes. ## Key Features * Read data from Filevine with advanced filtering (date ranges, case status, client name, employer name). * Write data into Filevine, including creating new records and updating existing ones. * Write back status updates from workflows into Filevine for real-time case management. * User-friendly interface for OAuth 2.0 authentication, field mapping, and configuration. * Field-level data validation to ensure compatibility with Filevine’s API. * Supports both scheduled and event-driven data synchronization. ## Supported Operations | Operation | Description | | --------- | --------------------------------------------------------------------------------------- | | Read | Retrieve records from Filevine with advanced filtering (date, status, client, employer) | | Write | Create new records in Filevine, with field-level validation and mapping | | Update | Updates the existing records in Filevine | **Field Mapping:** Use DBSync’s mapping interface to match source fields to Filevine fields for seamless data transfer. **Bidirectional Sync:** Ensure bi-directional data synchronization between Filevine and other systems. ## Prerequisites Before configuring the Filevine Connector, make sure the following are in place: 1. **DBSync Access** * A valid license for this connector and access to the DBSync Cloud Workflow platform. 2. **Filevine API Access** * A valid Filevine account with necessary read/write permissions. 3. **OAuth 2.0 credentials** * OAuth Client ID, Client Secret, and Access Token (obtained via OAuth flow). ## Connector Configuration Each Filevine connector instance represents a connection to a specific Filevine project or environment. If you have multiple Filevine instances (for example, sandbox vs. production), configure separate connectors. The Filevine Connector uses OAuth 2.0 for secure access. Once configured, DBSync securely stores the credentials and uses them to make authorized API calls for workflow execution. ## Connector Validation and Save {% stepper %} {% step %} ### Test Connection * Click Validate to verify credentials. * Click **Test Connection** to verify that credentials and permissions are valid. {% endstep %} {% step %} ### Save Configuration * Once validated, save the connector for use in workflows. After setup, Filevine data is available as a source or target in workflow triggers, tasks, and mappings. {% endstep %} {% endstepper %} ## Quick Setup Guide Follow these steps to configure the Filevine connector: {% stepper %} {% step %} ### 1. Login to DBSync Cloud Workflow Use your DBSync credentials to access the platform. {% endstep %} {% step %} ### 2. Add the Filevine Connector Navigate to the connectors list in the Apps pane and select **Filevine**. {% endstep %} {% step %} ### 3. Enter Authentication Details In the Filevine Connector configuration page, enter the required details: * STEP 1 1. **Client ID**: Public identifier for your application. 2. **Client Secret**: Confidential key for authentication. 3. **Personal Access Token (PAT):** Temporary credential for accessing protected resources, obtained after successful OAuth authentication. * STEP 2 1. **Organization**: From the drop down, select the required Organization.
{% endstep %} {% step %} ### Test Connection * Click **Validate** to verify credentials. * Click **Test Connection** to verify that credentials and permissions are valid. {% endstep %} {% step %} ### Save Configuration * Once validated, save the connector for use in workflows. After setup, Filevine data is available as a source or target in workflow triggers, tasks, and mappings. {% endstep %} {% endstepper %} ## Use Cases: Automated Project and Case Synchronization Between Filevine and CRM #### Objective Automatically create and update Filevine "projects" (cases) based on new client intakes or matter updates in your CRM, ensuring legal teams always have up-to-date case records and related information in Filevine. #### Scenario Overview In Filevine, every legal case or matter is represented as a project. Each project holds all relevant information for a case, including client contact details, documents, deadlines, tasks, and related parties. Legal firms often want to synchronize their CRM or intake system with Filevine to avoid manual data entry, reduce errors, and accelerate case onboarding. #### Workflow Steps {% stepper %} {% step %} #### 1. New Intake in CRM * A new client matter is created in your CRM or intake platform (for example, Salesforce, HubSpot, or a custom portal). {% endstep %} {% step %} #### 2. Trigger DBSync Workflow * DBSync detects the new client matter and triggers the flow. {% endstep %} {% step %} #### 3. Create Project in Filevine The connector creates a new "project" in Filevine, populating it with: * Project/client name and contact card * Case type (using the appropriate project template) * Key dates (intake date, incident date, deadlines) * Custom fields (e.g., claim number, opposing party) * Initial phase/status {% endstep %} {% step %} #### 4. Update Related Cases * If the CRM record indicates related matters (such as multiple plaintiffs in the same incident), the connector can create linked projects in Filevine and use the Related Projects feature to associate them. * For example, two clients involved in the same accident will each have their own Filevine project, but these are linked as related cases for easy navigation and reporting. {% endstep %} {% step %} #### 5. Ongoing Sync * Updates in the CRM (for example, change in client contact info, case status, or key dates) are automatically pushed to the corresponding Filevine project. * Status changes in Filevine (such as phase progression or case closure) can be written back to the CRM, keeping both systems in sync. {% endstep %} {% endstepper %} ## Best Practices * Use Filevine’s customizable project templates to ensure all required fields are captured during project creation. * Leverage the Related Projects feature to manage complex matters involving multiple parties or linked cases. * Schedule regular syncs or use event-driven triggers for timely updates. * Test your workflow with sample data to ensure correct mapping and data integrity. ## Troubleshooting * If the connection is lost, navigate to the **Connectors** section, select **Filevine**, and click **Reconnect**. Enter the authentication details and test again. * For mapping or data compatibility issues, verify field names and types in both DBSync and Filevine to ensure alignment. * For complex migrations or custom field mapping, consult Filevine’s documentation or your Implementation Consultant. *** ## Frequently Asked Questions (FAQ)
Can I connect multiple Filevine projects? Yes, create separate connector configurations for each project or environment you need to integrate.
Is the connector secure? Yes, Filevine API tokens are stored securely and all traffic occurs over encrypted HTTPS connections.
Does the connector support custom fields? Yes, workflows can leverage custom fields defined in Filevine for mapping and synchronization.
Can I set up bi-directional sync? Yes, workflows can be configured to sync data both ways between Filevine and other systems.
Do I need technical skills to configure the connector? The connector setup is guided and does not require advanced development skills. However, understanding your API credentials and object model is helpful.
Can I use multiple connectors in a single workflow? Yes, DBSync allows integration of multiple connectors for complex data operations.
How often can syncs be performed? Sync frequency is configurable using the DBSync scheduler. Refer to your DBSync plan for details.
*** ## Summary The Filevine Connector in DBSync Cloud Workflow provides a secure and flexible integration solution for syncing case management data, contacts, tasks, and related objects between Filevine and your enterprise ecosystem. By enabling automated workflows that connect Filevine with CRM, billing, document management, and analytics systems, organizations can reduce manual effort, enhance collaboration, and keep critical data synchronized across teams. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.mydbsync.com/cloud-workflow/2026_connectors_new/filevine.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.