Data Warehouse: Filevine Object Support and Limitations

  • Updated

 

This article provides an overview of the support and limitations for key objects managed within the Data Warehouse (DW) when integrated with Filevine. Each object — such as Forms, Collection Items, Projects, Contacts, and Documents — behaves differently in terms of data ingestion, updates, auditing, and webhook coverage. The goal is to help you understand what to expect when working with these records inside the Data Warehouse.

Throughout this article, you’ll find detailed information for each object, including its DW table name, hydration behavior, audit support, supported field types, and known limitations. We also cover how each object interacts with webhooks — which fields are included in webhook events, and what data might be missing due to Filevine’s integration behavior.

This article is designed as a quick reference for technical users, data teams, and developers working with Filevine integrations. Understanding these support details and limitations will help you anticipate system behavior, avoid common pitfalls, and build more reliable processes when consuming or analyzing Filevine data in your Data Warehouse.

 

Form Object — Support and Limitations

Category

 Details

Data Warehouse

Supported in DW

Yes, by webhook

DW Table Name

fvdw_Form_{project_type}_{section}
Used for storing form data. Includes project type and section name for clarity.
 

Hydrations

Limitations

Some fields may not populate fully or consistently due to general limitations in how data is imported (hydrated).
 

Updates 

 Limitations
None — this object is not restricted when updating records.
 

Audit 

Supported

Yes — Changes are tracked and logged for audit purposes.

Field Types Supported: 

  • Amount: Currency, Decimal, Number, Percent
  • Text: Single Line, Multi-Line (Large)
  • Other: Yes/No, Dropdown List, URL, Case Number, Phone, Email, Address

Limitations

Only fields that are available through the report builder are supported.

Webhook 

Supported

Yes — Webhooks are supported and send real-time updates.

Relevant Webhook Fields

When a webhook event is triggered, it includes the following fields:

  • Info about the event itself: 

    - webhookEvent

    - webhookTimestamp

    - webhookUserId

  • Timestamps for data creation and last update:

    - dwCreatedAt

    - dwUpdatedAt

Limitations

The field projectIdPartner is only available when requesting a single item (ITEM endpoint), not when retrieving a full list (LIST endpoint). This means it won't appear if you're pulling many forms at once.

Known Matters
  • Differences between single-item and list responses.
  • Occasional delays in receiving webhook events.

CollectionItem Object — Support and Limitations

Category Details

Data Warehouse

Supported in DW

Yes, by webhook

DW Table Name

fvdw_CollectionItem_{project_type}_{section}

Used for storing items within a Collection. Includes project type and section name for clarity.

Hydrations 

Limitations

Some fields may not populate fully or consistently due to general limitations in how data is imported (hydrated).
 

Updates 

Limitations

None — this object is not restricted when updating records.

Audit

Supported

Yes — Changes are tracked and logged for audit purposes.

The audit relies on the Filevine report List of {sectionName} Items tied to each collection.

Field Types Supported 

  • Amount: Currency, Decimal, Number, Percent
  • Text: Single Line, Multi-Line (Large)
  • Other: Yes/No, Dropdown List, URL, Case Number, Phone, Email, Address

Limitations

  • The audit only applies to field types available in the report.
  • The “Undeleted” webhook event is not supported.
  • Only fields available in the Filevine “List of {sectionName} Items” report are audited and supported.

Webhook

Supported

Yes — Webhooks are supported and send real-time updates.

Field Types Supported 

When a webhook event is triggered, it includes the following fields:

Event Info: 

  • webhookEvent
  • webhookTimestamp
  • webhookUserId

Timestamps: 

  • dwCreatedAt
  • dwUpdatedAt

Field Supported

By webhook: 

  • sectionSelector
  • section_executedAt
  • section_resetAt
  • section_resetBy
  • section_executedBy

By other logic: N/A

By API: N/A

Limitations

The field projectIdPartner is only available in ITEM endpoints, not in LIST responses. It is only populated through webhook events.

Known Matters
  • Differences between single-item and list responses
  • The “Undeleted” event is not supported
  • Webhook event timing may vary


Taskflow Object — Support and Limitations

Category Details

Data Warehouse

Supported in DW

Yes, by webhook

DW Table Name

fvdw_Form_{project_type}_{section}
fvdw_Collection_{project_type}_{section}

Taskflow events are captured within form and collection tables.

Hydrations 

Limitations

N/A — Taskflow data is not hydrated from the API; it relies exclusively on webhook events for taskflow-related timestamps.

Updates

Limitations

None — this object is not restricted when updating records.

Audit

Supported

No — Changes to taskflow fields are not audited.

Limitations

These fields are only populated by webhook events. They are not available via the Filevine API and are not hydrated through standard import processes.

Webhook

Supported

Yes — Webhook events are the only source of Taskflow data in the Data Warehouse.

Field Types Supported

Taskflow-specific system fields:

By webhook:

  • sectionSelector

By other logic:

  • section_executedAt
  • section_executedBy
  • section_resetAt
  • section_resetBy

By API: N/A

Limitations

  • Taskflow dates and activity are written only through webhook data.
  • These fields are not returned in Filevine API responses (neither LIST nor ITEM).

Known Matters
  • Taskflow fields depend entirely on webhook events.
  • No audit log or fallback via API or report.
  • Not available in LIST/ITEM API responses.

Project Object — Support and Limitations

Category Details

Data Warehouse

Supported in DW

Yes, by webhook
 

DW Table Name

fvdw_Project

This table stores general project information from Filevine.

Hydration

Limitations

Some project fields may not populate or update due to how webhook events are triggered.

Update Limitations

Limitations

None — this object is not restricted when updating records.

Audit

Supported

Yes — Changes to project data are tracked and logged for audit purposes.
 

Audit Limitations

Audit compares values from the Filevine report List of Projects. Supported fields include:
 

  • projectId
  • projectName
  • clientId
  • createdDate
  • phaseName
  • clientName
  • firstPrimaryName
  • lastActivity
  • uniqueKey
  • projectOrClientName
  • Hashtags
  • projectEmailAddress
  • projectUrl
  • phaseDate
  • incidentDate

Field Types Supported

Fields listed in the Filevine List of Projects report. See above for details.

Field Limitations

The webhook event updated is not triggered in certain cases:

  • When hashtags are added via API.
  • When the first primary user changes.
  • When the project contact changes.

Webhook

Supported

Yes — Webhooks are supported and deliver project-level updates.

Field Types Supported

Webhook-delivered fields include date and phase info not available in the API:

phaseDater and similar values are populated only via webhook.

Limitations

  • Some fields (like phaseDater) are only included in webhook events, not in LIST or ITEM API responses.
  • Updates may be skipped if Filevine does not emit the expected webhook event.

Known Matters
  • Webhook updated event not triggered in key scenarios (see above)
  • Differences between webhook data and API availability for certain fields

Contact Object — Support and Limitations

Category Details

Data Warehouse

Supported in DW

Yes, by webhook

DW Table Name

fvdw_Contact_legacy

fvdw_Contact_{tab_id}

Contacts are stored in a legacy table and one or more custom tab tables depending on configuration.

Hydrations

Limitations

Some contact fields may not populate due to webhook behavior and Filevine limitations.

Update

Limitations

None — this object is not restricted when updating records.

Audit

Limitations

Yes — Changes are tracked and logged for audit purposes.

Audit Limitations

  • Custom contact tabs are not supported in audit comparisons by ID or value.
  • Audit relies on Filevine’s “Marketing List” report, which does not include archived contacts.

Supported fields include: 

  • firstName
  • middleName
  • lastName
  • Nickname
  • fullName
  • primaryEmail
  • birthDate
  • deathDate
  • fromCompany
  • Phones
  • Emails
  • Prefix
  • Suffix
  • Salutation
  • Hashtags
  • jobTitle
  • Department
  • isDeceased
  • Ssn
  • Notes
  • Gender
  • Language
  • maritalStatus
  • driversLicenseNumber
  • Fiduciary
  • isMinor
  • Remarket
  • barNumber
  • isTextingPermitted
  • specialty
Field Types Supported
All standard fields listed above from the Marketing List report. Custom fields are only partially supported depending on webhook payload.

Field Limitations

  • The Created webhook is not triggered when a contact is created via the legacy contact API — so the DW won’t reflect it.
  • Archived webhook events are not supported.
  • Contact TabIe is missing from the “updated” event payload, so all tables are updated to ensure data accuracy.

Webhook

Supported

Yes — Webhooks are supported and used for real-time updates

Field Types Supported

Typical webhook fields include creation and update timestamps, user data, and standard contact field updates.

Tab-related information is limited in some webhook events.

Limitations

  • Archived contacts appear in the API but are excluded from the Marketing List report.
  • Custom tab changes are applied but not included in audit comparisons.
  • Missing tabId causes updates to apply across all tab tables.

Known Matters
  • Created event missing for legacy API-created contacts.
  • Archived webhook not available.
  • Missing tabId in updates leads to broad table updates.
  • Audit does not validate custom tab data.

Document Object — Support and Limitations

Category Details

Data Warehouse

Supported in DW

Yes, by webhook

DW Table Name
fvdw_Document

This table stores document metadata for files uploaded in Filevine.

Hydration 

Limitations

Not applicable — data is captured directly through webhook events.

Update

Limitations

None — this object is not restricted when updating records.

Audit

Supported

Yes — Changes to documents are tracked and logged for audit purposes.

Audit Limitations

Audit uses Filevine’s List of Docs report and includes:
 

  • documentId
  • Filename
  • Size
  • uploaderFullname
  • uploadDate
  • hashtags
Field Types Supported
Standard fields included in the document report above.

Field Limitations

  • The deleted event is not triggered when a file is deleted through the section UI.
  • No webhook is received when a document is moved by moving a related note.
  • undeleted and related webhook events are not supported.
  • To track document movement, the system listens to note movement events and updates the document accordingly.

Webhook 

Supported

Yes — Webhooks are supported and used for document creation, updates, and some deletion events.

Field Types Supported

Refer to Filevine webhook documentation for full event list:

Limitations

  • Document movements caused by note actions are tracked via note webhooks, not document webhooks.
  • Events like undeleted and related are not supported, so those changes won't be reflected.

Known Matters
  • No webhook on section UI deletion.
  • Movement via notes does not trigger document update webhook.
  • Certain events unsupported: undeleted, related.

 

Note Object — Support and Limitations

Category Details

Data Warehouse

Supported in DW

Yes, by webhook

DW Table Name

fvdw_Note

This table stores comment and note activity created in Filevine projects.

Hydration

Limitations

Notes marked as Reminders are not included in the list endpoint and do not trigger webhook events — therefore, they are excluded from the DW.

Update

Limitations

None — this object is not restricted when updating records.

Audit

Supported

Yes — Changes to notes are tracked and logged for audit purposes.

Audit Limitations

Notes marked as Reminders are excluded from the audit process.

Audit compares data from the Filevine List of Notes report, including:

  • noteId
  • typeTag
  • Body
  • createdAt
  • lastActivity
  • isPinnedToProject
  • isPinnedToFeed

Field Types Supported

Standard note metadata fields listed above, as available through the List of Notes report.

Field Limitations

  • The Assigned webhook is not triggered when a task is reassigned via an @mention in a comment.
  • Notes marked as Reminders are excluded from both API list endpoints and webhook coverage.

Webhook Support

Supported

Yes — Webhooks are supported and used for creating and updating note records.

Field Types Supported

Refer to Filevine webhook documentation:

Limitations

  • Reminder-type notes are excluded from both API list and webhook events, so their data cannot be hydrated or audited.
  • Reassignment via @mention does not trigger an Assigned webhook event.

Known Matters
  • Reminder notes are excluded
  • Missing “Assigned” event for reassignment via comment
  • Limited webhook visibility for specific note actions

 

Project Deadline Object — Support and Limitations

Category Details

Data Warehouse

Supported in DW

Yes, by webhook

DW Table Name

fvdw_Deadline

This table stores deadline-related information tied to Filevine projects.

Hydration

Limitations

Not applicable — deadlines are written directly from webhook events.

Update

Limitations

None — this object is not restricted when updating records.

Audit

 Supported
No — Project deadline data is not audited.

Audit Limitations

Not applicable — no audit support is currently implemented for this object.

Field Types Supported

Standard project deadline fields as exposed through Filevine and supported by the webhook events.

Field Limitations

The MassUpdated webhook event is not supported, as it does not provide enough detail to correctly update records in the Data Warehouse.

Webhook

Supported

Yes — Webhooks are supported and used to create and update project deadline data.

Field Types Supported

Standard deadline creation and update fields (timestamps, user data, deadline attributes) as included in supported webhook payloads.

Limitations

The MassUpdated event is ignored due to insufficient information in the payload to apply updates reliably.

Known Matters
  • Lack of support for mass update events
  • All deadline data relies entirely on individual webhook events


Toggle Object — Support and Limitations

Category Details

Data Warehouse

Supported in DW

Yes, by webhook

DW Table Name

fvdw_Section

This table captures Toggle actions (such as visibility changes) triggered by users within Filevine sections.

Hydration

Limitations

Not applicable — toggle data is written only from webhook events. 
 

Update

Limitations

None — this object is not restricted when updating records.

Audit

Supported

No — Toggle data is not audited, as records are continuously overwritten and historical tracking is not supported.

Audit Limitations

Not applicable — auditing is not available for toggles due to schema overwrite behavior.

Field Types Supported

Toggle events include the following fields:
 

  • webhookEvent
  • webhookObject
  • webhookObjectId
  • webhookOther
  • webhookTimestamp
  • webhookUserId
  • orgId
  • projectId
  • Visibility
  • sectionSelector
  • projectTypeId
  • dwCreatedAt
  • dwUpdatedAt

Field Limitations

  • Data is sourced exclusively from webhook payloads.
  • There is no API or report support for this object.
  • Historical values are not stored, only the latest toggle is kept.

Webhook Support

Supported

Yes — Webhooks are the only data source for toggle actions.

Field Types Supported

See fields listed above — all values are taken directly from the toggle webhook payload.

Limitations

  • The webhook event for toggles is always identified as event: toggle.
  • Historical tracking is not possible because incoming events overwrite previous data.

Known Matters
  • No audit or hydration support
  • Only latest toggle state is stored
  • Historical changes cannot be recovered

 

ProjectType Object — Support and Limitations

Category Details





 

Data Warehouse

Supported in DW

Yes, but only via manual schema initialization (init).

DW Table Name
fvdw_ProjectType

This table stores information about project types and their configuration in Filevine.

Hydration Limitations

Limitations

This object is not hydrated automatically. It is only updated when the schema init process is manually triggered.

Update Limitations

Limitations

None — this object is not restricted when updating records.

Audit Supported

Supported

No — ProjectType data is not audited.

Audit Limitations

Not applicable — no audit process is in place for this object.

Field Types Supported

Standard schema metadata fields: 

  • dwCreatedAt
  • dwUpdatedAt
  • The rest of the project type configuration fields.

Field Limitations

  • No webhook events are triggered for changes to project types.
  • When a new section field is added in the UI, the schema is not updated automatically — a manual schema init is required.

Webhook Support

Supported

No — This object is not supported by webhook events.

Filed Type Supported

Not applicable — no webhook events are available for this object.

Limitations

  • The table is only populated and refreshed when the schema initialization process is run.
  • This object will not reflect changes (like new section fields) until the schema is manually reloaded.

Known Matters
  • No automatic updates from Filevine.
  • Schema must be re-initialized to reflect changes.
  • No audit or webhook tracking available.


Project Chain Deadline Object — Support and Limitations

Category Details

Data Warehouse

Supported in DW

Yes, by webhook
 

DW Table Name

fvdw_ChainDeadline

This table stores information related to deadlines managed within project chains in Filevine.

Hydration

Limitations

Not applicable — data is written exclusively via webhook events.

Update

Limitations

None — this object is not restricted when updating records.

Audit

Supported

No — Project Chain Deadline data is not audited.

Field Types Supported

Fields include:

  • webhookEvent
  • webhookTimestamp
  • webhookUserId
  • doneDate
  • dateValue
  • dwCreatedAt
  • dwUpdatedAt
  • Other standard ChainDeadline metadata fields

Field Limitations

  • This table is maintained only through webhook events.
  • The webhook events Deleted and Undeleted are not supported, so deletions or restorations won’t be reflected in DW.

Webhook

Supported

Yes — Webhooks are used to create and update chain deadline records.

Field Types Supported

Core fields listed above, included in standard ChainDeadline webhook payloads.

Limitations

  • Deletion and undeletion actions are not captured, due to lack of webhook support.
  • Changes are tracked only when supported webhook events are triggered.

Known Matters
  • No support for Deleted and Undeleted events.
  • No auditing capabilities.
  • Relies entirely on webhook data for updates.

Project Sections and Fields Object — Support and Limitations

Category Details
Data Warehouse

Supported in DW

Yes, but only via manual schema initialization (init)

DW Table Names

fvdw_ProjectType_Sections — stores metadata about section configuration in each project type.

fvdw_ProjectType_Fields — stores metadata about field configuration within those sections.

Hydration

Limitations 

Data is not updated automatically. These tables are only refreshed when the schema init process is manually triggered.
Update

Limitations

None — this object is not restricted when updating records.
Audit

Limitations

No — Project section and field metadata is not audited.

Audit Limitations

Not applicable — audit process does not apply to these configuration tables.

Field Types Supported

Schema metadata fields such as:

  • dwCreatedAt
  • dwUpdatedAt
  • Configuration details for each section and field.

Field Limitations

  • No webhook events are emitted by Filevine for changes to sections or fields.
  • When a new field or section is added in the UI, it will not appear in DW until a schema init is rerun.
Webhook

Supported

No — These objects are not supported by webhook events.

Field Types Supported

Not applicable — no webhook fields are used for these tables.

Limitations

  • Schema data is only accurate after running a manual schema init.
  • Changes made in the Filevine UI (e.g., adding a field) will not sync automatically to DW.
Known Matters
  • No automatic hydration
  • No webhook or audit support
  • Manual schema re-initialization is required to reflect any configuration changes