Skip to content
docivault

Integrations and import

Integrations, import and connectors

Can docivault import documents I already have somewhere else?

Not yet. Uploading from your device is built and available now, but pulling documents across from Google Drive, OneDrive or an inbox is not, and neither is accepting one over WhatsApp, Telegram, Slack or email. Those import paths and connectors are what this page is about.
Coming soon

The problem

Your documents are already somewhere, and the other side already has a habit

  • Documents already live somewhere else

    Years of files sit in a Google Drive, a OneDrive, or scattered across an inbox — moving into a new tool feels like it means re-uploading all of it by hand.

  • People will not switch where they send from

    The person sending you a document already has a habit — WhatsApp, Telegram, Slack, plain email — and asking them to change it is the thing most likely to make them not send it at all.

  • No way to reach in programmatically

    A team that wants to script part of its document workflow, or point an AI agent at it, has nothing to connect to.

Import

Bring in what already exists, instead of re-uploading it by hand

Not built yet — next up, no date promised.

  • Import from Drive, OneDrive and email

    Coming soon

    Bring documents you already have in Google Drive, OneDrive or an inbox into a workspace.

Connectors

Accept a document from wherever the other side already sends it

On the roadmap — not built, not scheduled.

  • WhatsApp, Telegram, Slack and email connectors

    On the roadmap

    Accept a document from wherever the other side already sends it, and file it in the right place.

API

A way to reach in programmatically, for scripts and AI agents

On the roadmap — not built, not scheduled.

  • Public API

    On the roadmap

    Documented HTTP endpoints, plus an MCP server for AI agents.

Questions

What people ask about integrations

Can docivault import documents I already have somewhere else?

Not in bulk, not yet. Bringing in files already sitting in Google Drive, OneDrive or an inbox is on the next-up list — not built, no date promised. Uploading from your own device is built and available now, so the gap is the automatic transfer, not the getting-documents-in.

Can the other side send me a document over WhatsApp or Slack instead?

Not today. Connectors that accept a document from WhatsApp, Telegram, Slack or email and file it in the right place are on the roadmap — an intention, not something scheduled or built.

Is there an API?

Not yet. A public API and an MCP server for AI agents are on the roadmap. Neither exists today, so there is nothing to call and nothing to point an agent at.

How do I get a document into docivault right now?

You upload it from your device, into whichever of a contact’s three spaces you choose. That is built and available now. What is not built is bringing documents across automatically from Drive, OneDrive or an inbox, or having the other side send one over WhatsApp or Slack — those are the import paths and connectors on this page.

Nothing to import into yet — set up the workspace first

Accept a document from wherever the other side already sends it, and file it in the right place. Documented HTTP endpoints, plus an MCP server for AI agents. Document upload has to ship before any of this does.

  • No credit card
  • Free plan, no expiry
  • The people you exchange with are free