10 live connectors · capabilities by plan

Features by connector

Pick a connector to see exactly what Claude can read and write — and filter by plan tier to see which capabilities are included in Solo or unlock at Team+. Every tool is a slice of real work you can hand off in plain English and review before it lands in the system of record.

Your Filevine projects, hand-off-able to Claude

Cohesive360 exposes your Filevine tenant to Claude through 32 purpose-built tools across 10 capability areas. Projects (read + update), contacts, notes, tasks, calendar, deadlines, document metadata, case team management, firm user directory, and Collections — Filevine's per-project-type custom data sections — with both reads and tenant-aware updates. Bound to your firm's API key, region-pinned to US or Canada, with writes that draft for review before they commit.

Projects, not tabs

Filevine calls cases 'projects' — the connector lets Claude search and open them, pull the case team, scan deadlines, draft notes, and create tasks without you clicking through a dozen tabs.

Per-user API key, scoped by your seat

Connect with an API Key + Secret generated inside Filevine's admin Settings → Integrations panel. Permission scope is whatever the admin who generated the key has — Claude inherits exactly that surface, no more.

US + Canada — pinned to one org

Tokens are region-scoped and your connection is pinned to one org. Switch orgs by disconnecting + reconnecting; multi-org users can keep a separate Cohesive360 seat per Filevine tenant if needed.

Filter by plan36 tools in view

Plan tiers gate capability areas, not API access scope. For pricing, see the Pricing page.

Capabilities

10 workflow areas. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.

Pill colors indicate API access scopeReadread-onlyRead + Writeread & writeLimitedpartial — see card heads-up

Projects (cases / matters)

Read + Write · 6 toolsSolo +

Find, open, read, and UPDATE Filevine projects by status, name, or client. Pull project detail with the assigned case team and the project's type / phase. Update name, status, client reference, or incident date — Filevine's term for a case is 'project' (same concept, different vocabulary).

What you can ask Claude

  • Show me my open projects
  • Find the Smith v. Jones PI project
  • Pull the full case team on the Garcia project
  • Close the Lopez project — settlement finalized
  • Update the incident date on Johnson v. Hospital to 2025-12-08

Underlying tools (6)

list_projectssearch_projectsget_projectget_project_teamlist_project_typesupdate_project

Contacts — directory + project-scoped

Read + Write · 5 toolsSolo +

Read the firm's Filevine contact directory and the per-project contact list. Create new contacts, and attach existing contacts to projects with a role (Treating Physician, Adjuster, Opposing Counsel, etc.) — supported in chat without leaving Claude.

What you can ask Claude

  • Look up the Garcia client's contact card
  • Show me every contact on the Smith v. Jones project
  • Create a Person contact for Maria Lopez — email + phone
  • Attach Dr. Patel as the treating physician on the Garcia project

Underlying tools (5)

list_contactsget_contactget_project_contactscreate_contactadd_contact_to_project

Notes — the project Activity Feed

Read + Write · 3 toolsSolo +

Read activity-feed entries on a project, write new notes (phone-call summaries, status updates, client communication memos), and edit existing notes when the file needs a correction. All entries flow into Filevine's standard Activity Feed.

What you can ask Claude

  • Pull the last 20 notes on the Garcia project
  • Write a note to the Lopez project: 'Spoke with adjuster — $45K offer rejected'
  • Catch me up on Smith v. Jones since last Monday
  • Fix yesterday's note on Johnson — should say '$85K offer' not '$58K'

Underlying tools (3)

get_project_notescreate_noteupdate_note

Tasks

Read + Write · 3 toolsSolo +

Surface what's open on a project, create new tasks with due dates, assignees, and descriptions, and update or close existing tasks (mark complete, reassign, push the due date).

What you can ask Claude

  • What tasks are open on the Garcia project
  • Create a task on Smith v. Jones: 'Order MRI records from St. Joseph's' due Friday, assign to me
  • Mark the medical-records-request task on Johnson as complete
  • Push the demand-letter task on Lopez to next Thursday

Underlying tools (3)

get_project_taskscreate_taskupdate_task

Calendar appointments

Read + Write · 2 toolsSolo +

Read scheduled appointments on a project (depositions, mediations, court dates, internal meetings) and create new ones with ISO 8601 UTC start/end times.

What you can ask Claude

  • What's on the calendar for Garcia next week
  • Schedule a deposition on Smith v. Jones for July 12 at 10am Eastern, conference room B
  • Add a mediation to the Lopez project — June 24, 2pm-5pm

Underlying tools (2)

get_project_appointmentscreate_appointment

Deadlines

Read + Write · 2 toolsSolo +

Read statutory + custom deadlines on a project and create new ones. Reminder rules + assignees inherit from the firm's deadline-rule defaults — you set the date, Filevine handles the cascading reminder schedule.

What you can ask Claude

  • What deadlines are coming up on Garcia in the next 30 days
  • Add a deadline to Smith v. Jones: 'Statute of limitations' due 2027-03-15
  • Create a discovery-cutoff deadline on Lopez for 90 days from today

Underlying tools (2)

get_project_deadlinescreate_deadline

Case team management

Read + Write · 6 toolsSolo +

Add staff to a project, change their roles (attorney, paralegal, intake, billing, etc.), and remove team members when matters close. Pair with list_users to look up Filevine user IDs by name or email.

What you can ask Claude

  • Add Sarah Wong to the Garcia project as a paralegal
  • Change my role on Lopez from associate to lead attorney
  • Who's on the Johnson case team — and what are their roles

Underlying tools (6)

get_project_teamadd_team_memberupdate_team_member_roleremove_team_memberlist_usersget_user

Collections — your firm's custom data sections

Read + Write · 4 toolsTeam +

Filevine's Collections are the per-project-type custom data sections firms model their workflows in — medical providers, witnesses, defendants, damages calculations, lien tracking. The connector exposes discovery (list project types → list sections → read items) plus an update path.

What you can ask Claude

  • List the custom sections defined on the Garcia project's project type
  • Pull every medical provider on the Lopez project
  • Update the treatment-end-date on the Tampa General entry to last Friday

Underlying tools (4)

list_project_typesget_project_type_sectionsget_project_collection_itemsupdate_collection_item

Firm directory (users / staff)

Read · 3 toolsSolo +

Read the firm's Filevine user roster — name, email, role, license type. Used by Claude to resolve names to user IDs before assigning tasks, adding team members, or filtering work-in-progress by assignee.

What you can ask Claude

  • Who are the attorneys at our firm in Filevine
  • Look up Sarah Wong's Filevine user id
  • List all paralegals on the team

Underlying tools (3)

list_usersget_userwho_am_i

Documents

Read · 2 toolsSolo +

List documents attached to a project and pull metadata for any single file — name, filename, size, content type, timestamps, latest revision. Document binary upload + download is Phase 0.2.

What you can ask Claude

  • What documents are filed on the Garcia project
  • Show me every PDF on Smith v. Jones from this month
  • Pull the metadata on document 88421
Heads up. Document upload + download lands in Phase 0.2. Phase 0.1.x ships listing + metadata so you can see what's filed and reference it in chat.

Underlying tools (2)

get_project_documentsget_document

Limits and roadmap

What the Filevineconnector can't do today, and why. We update this when things change.

Pending vendor support

Documented endpoints that currently fail on production tenants. Support tickets open; vendor UIs work as the fallback.

  • Authorization Code (OIDC) flow. Filevine supports OAuth 2.0 Authorization Code + PKCE for registered partner apps. We've built the helper but the live partner-app registration is pending Filevine's developer-relations approval.

On the roadmap

Technically possible but not yet prioritised. Email product@cohesive360.com if any of these would change your decision to roll out.

  • Document upload + download. Filevine uses a two-step pre-signed-URL flow for binary files. The platform-side binary streaming layer is the same one powering SA + Clio document handlers; we're wiring Filevine through it in Phase 0.2.
  • Collection item CREATE / DELETE. Phase 0.1.1 ships Collections read (get_project_type_sections + get_project_collection_items) and update (update_collection_item). Creating + deleting items are Phase 0.2.
  • Time entries + billing. Filevine has a billing module. Surface is large; we'll prioritise it after the binary-document work lands.

Safeguards built into the connector

Defensive behaviours we put in the client because the underlying systems don't.

PAT-based auth — revocable from Filevine

Connect with an API Key + Secret. The key is bound to one Filevine admin user; the firm can revoke it instantly from Settings → Integrations → API Keys and the connector loses access on the next call.

Encrypted credential vault

Your API key + secret are stored in our credential vault: AES-256-GCM encrypted, master key in Azure Key Vault, ciphertext bound to your user ID + connector slug — a stolen blob can't be decrypted as another connector's credentials.

Permissions inherit the key owner's role

Filevine's API runs as the user who created the key. If that user can't see or edit a project in the Filevine UI, Claude can't reach it through the connector either.

1-hour bearer with proactive refresh

Filevine issues 1-hour bearer tokens via OAuth 2.0 client_credentials. The connector refreshes ~60s before expiry to keep calls smooth and falls back to exponential backoff on 429 with up to three retries.

Writes preview before commit

Notes, tasks, appointments, deadlines, and contacts all draft for review by default. You see the payload Claude is about to POST; one nod commits it through the API.

What Filevine via Cohesive360 is not

Honest boundaries — what Claude through this connector cannot guarantee.

Cohesive360 is a facilitation channel between Claude (Anthropic) and your Filevinetenant. Claude's responses are Anthropic's output; the underlying data is the vendor's system of record. We transport requests and responses; we do not generate, review, or validate Claude's output, and we do not operate the vendor's API.

Claude can be wrong. It can misread a record, misinterpret a date, draft against the wrong matter, or summarise incorrectly. Treat every draft as a draft — review it before you accept it, particularly anything that affects a deadline, a client communication, or a matter already in motion.

The vendor can be unavailable. The API can rate-limit, return errors, or reject requests for reasons specific to your tenant configuration. When that happens, Claude will tell you — but we have no control over when or why the vendor refuses a call.

Ready to put Claude on your firm's tools?

Two minutes from creating an account to your first answer.