Video on the Drupal Site Without a Module
No Drupal module exists for this, and none is needed. The connection is an embed code and a JavaScript widget placed in a page, which is the same path the shipped WordPress and SharePoint integrations run on, and it works on any site that renders HTML. Drupal runs a great many government and university sites, usually chosen for a permission model that matches how the organization is arranged and run by a team that owns the site outright. Nexus, the portal behind the Enterprise Video Platform (EnterpriseTube) solution, holds the recordings under their own access rules, and Drupal keeps the site.
How it connects
Nothing is installed in Drupal. An editor pastes a widget or an embed code into a block, a node or a page template the way they paste any other markup.
More than a player is available to place. The documented widgets cover video, audio, image, document, collection and playlist players, media library gallery and detail views, insights, transcription, maps, carousel and collage, quiz and survey players, and a mashup filter. A Drupal page can therefore carry a browsable library or a search view rather than one recording at a time.
Configuration stays in Nexus. Embedding is restricted to approved domains, either everything except a blocklist or nothing except an allowlist, so widgets render on the sites you name and are refused elsewhere, and content URLs are signed and expire. Each embed resolves against the viewer's identity, so a recording restricted in Nexus stays restricted on the Drupal page carrying it. Drupal's own users and permissions go on governing the page itself.
What does not exist is the other direction. There is no ingestion connector for Drupal, so content held in Drupal is not pulled into the library. Ingestion is a per-source connector and the built ones are SharePoint, OneDrive, Kaltura, Azure Blob, AWS S3 and Teams. Where a Drupal site's own media needs to come under governance, that is a piece of work scoped per engagement rather than a setting.
What you can do together
- Publish without a second upload: an editor pastes an embed into a node and the recording streams from Nexus, so nothing lands in Drupal's file system.
- Put a whole library on a page, with gallery, detail and search widgets giving a department a browsable set instead of a list of links somebody maintains.
- Keep a restricted recording restricted on a page anyone can open, because the embed resolves against the viewer.
- See which page carries the audience, since embed analytics report where an item is embedded, the view count per site and the last playback from it.
A scenario
- SetupAn administrator adds both sites to the approved domain list in Nexus. Nothing is installed in Drupal.
- Tuesday eveningThe clerk uploads the council meeting recording to Nexus, sets it public, and files it under the retention rule the records policy calls for.
- Wednesday morningThe editor pastes the player widget into the meeting's Drupal node, then a gallery and a search widget onto the meetings landing page, so residents browse past meetings without leaving the city site.
- The same weekA work-zone briefing limited to public works staff is embedded on the intranet. A resident who finds that page sees the page and not the video.
- Quarter endEmbed analytics show which of the two sites actually carried the audience.
What stays where
Drupal keeps the site
Pages, blocks, menus, users and the permission model that made Drupal the choice stay where they are, and no module is installed for a widget to render.
The media stays in the library
Files, access rules, retention and analytics live in Nexus, and the page renders a view rather than a copy.
Ingestion from Drupal does not exist
Surfacing content on the site ships; pulling Drupal's own content into the library is a connector that has not been built.
Processing runs where you deploy the platform
Shared or dedicated SaaS, your own cloud subscription, or on premises. Visitors reach the player over the network, so a public site needs a deployment reachable publicly.
Products and solutions
Next step
See it on your own Drupal 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/drupal