VIDIZMO integration brief · SharePoint · vidizmo.ai/integrations/catalog/sharepoint

Integrations / SharePoint

SharePoint

SharePoint as both a content source and an export destination. Visit website

SharePoint is where most organisations keep documents and run internal sites.

Libraries act as a source, so material already filed there is ingested, indexed and transcribed, and as a destination, so processed output lands back where people expect to find it.

Video Filed in SharePoint, Transcribed and Searchable

Open as a two-page brief

SharePoint is where the documents are filed and the internal sites run, and where recordings end up when nobody has decided otherwise. With Nexus connected, the portal behind the Enterprise Video Platform (EnterpriseTube) solution, a SharePoint library becomes a source: what is filed there is ingested, transcribed and indexed. It is also a destination, so processed output lands back in the library where people expect it. Players and library views embed into SharePoint pages as well. SharePoint stays the file store and the intranet.

How it connects

Three connections, used alone or together. The Ingestion connector reads a SharePoint library on a schedule or continuously. Which paths are included and excluded, which file extensions are accepted, and whether the folder structure is preserved or flattened are configured in Nexus, along with what happens to the source file afterwards: left in place, moved, or deleted. Each file becomes a Nexus library item, transcribed and indexed.

The Export connector goes the other way. Processed output is written to a SharePoint destination, and every export is logged.

The JavaScript widget places a player, a library view, search or an interactive element into a SharePoint page. The page stays in SharePoint, the media streams from Nexus, and each embed resolves against the viewer's identity, so access control travels with it.

The same Microsoft 365 integration reaches Teams recordings, which ingest automatically, and OneDrive folders, which serve as sources and export destinations.

What you can do together

  • Turn a library of training recordings into something searchable. Nexus ingests what is filed there, transcribes it and indexes it, so a nurse searches for the procedure rather than scrolling a folder.
  • Leave the filing as it is. The Nexus connector runs on a schedule or continuously, preserves or flattens the folder structure as you choose, and leaves, moves or deletes the source file as you choose.
  • Put the Nexus player on the intranet page staff already open, with search and a library view beside it.
  • Send output back. A recording processed in Nexus lands in the SharePoint library you name, and the export is logged.
  • Bring Teams recordings and OneDrive folders into Nexus through the same Microsoft 365 integration.

A scenario

  1. SetupThe SharePoint administrator points the Ingestion connector in Nexus at the education library, includes the two folders that matter, accepts video and audio extensions, keeps the folder structure and leaves the source files in place.
  2. OvernightThe connector runs and every recording becomes a Nexus library item, transcribed and indexed, under the education team's retention rule and permissions.
  3. Next morningAn educator adds the player widget and the search widget to the education site's home page in SharePoint. The intranet domain is approved, so the page renders them.
  4. The same dayA nurse opens the page, searches for a procedure, and plays the session that covers it. She never left SharePoint.
  5. Each weekNew recordings dropped into the library are picked up on the schedule. The educator exports a processed recording back to a library shared with another campus, and the export is logged.

What stays where

SharePoint keeps the files and the sites

Libraries, pages, permissions and the Microsoft 365 tenant stay as they are. Whether a source file is left, moved or deleted after ingestion is your setting.

Nexus reads and writes

It reads the libraries the connector is pointed at, writes what an export sends, and streams to the widgets on your pages.

Nothing is replaced

SharePoint remains the document store and the intranet. Nexus holds the video with its transcript, index, retention and access rules.

Processing runs where you choose

Nexus is offered as shared SaaS, a dedicated instance, in your own cloud or on your own servers.

Products and solutions

Next step

See it on your own SharePoint instance. We will show the connection made, the data moving and the output, then size it for your deployment.

Request a demonstration  or write to sales@vidizmo.ai

sales@vidizmo.ai  ·  vidizmo.ai/integrations/catalog/sharepoint

Not what you need?

We build it

Send us your API documentation and we build, test and maintain the connector, at no development cost to you.

Request this integration

Bring an MCP server

If the system publishes a Model Context Protocol server, AI Intelligence Hub connects to it as a client with configuration alone.

Define a REST endpoint

Describe your endpoint and it becomes a node in an agent workflow, without waiting on our roadmap.

Product names, logos and trademarks shown here are the property of their respective owners. Their use does not imply any affiliation with or endorsement by them.