Summary: Connecting your digital asset management (DAM) system to Korbyt puts approved, on-brand content on the right screens automatically. This guide covers four ways to do it: Couriers, the SharePoint Adapter, URL and HTML elements, and the Korbyt API. It also covers how to set up your rules and which pitfalls to avoid.
Digital asset management (DAM) and digital signage may seem like separate technologies at first glance, but together they form a powerful duo for delivering impactful visual communications. Both are built around maximizing the value of content. DAM organizes and optimizes assets, and digital signage broadcasts them to the right audience at the right time.
When integrated with digital signage using a content management system (CMS) like Korbyt, a DAM system can streamline workflows, ensure brand consistency, and supercharge the speed and effectiveness of content delivery across screens. This article explores how connecting a DAM to your CMS streamlines asset usage across signage campaigns. Automatically surfacing approved, up-to-date visuals and reducing manual content uploads and time to delivery.
By centralizing access to brand-compliant media, teams eliminate outdated content, keep branding consistent, accelerate publishing workflows, and unlock more dynamic communications. In other words, the right content is seen on the right screen with minimal hands-on effort.
How to Integrate a DAM System with Korbyt CMS
There are four ways to connect a DAM to Korbyt. The right one depends on where your assets live and how much control you need over timing and metadata.
| Method | Best for | How content syncs | Setup effort |
| Courier | DAMs and cloud storage that Couriers support, like Adobe Experience Manager, Box, Dropbox, Google Drive, and Microsoft OneDrive | On a schedule: every 30 minutes, hourly, or daily | Low. Log in to the service and pick a folder. |
| SharePoint Adapter | Organizations using SharePoint as their DAM or content repository | Pulls files plus playlist and scheduling details from SharePoint | Moderate. Follows a guided setup. |
| URL and HTML elements | DAMs that publish content as a URL or embeddable HTML | Live. Screens show the latest published version. | Low. Add an element in Layout Builder. |
| Korbyt API | Any DAM, especially ones with custom metadata or approval workflows | As soon as an asset is approved, or on a schedule you set | Higher. Needs a developer or an integration platform. |
1. Korbyt’s Courier Integration
The easiest way to integrate an enterprise DAM system with Korbyt Anywhere is through our easy-to-use Courier system. A Courier is Korbyt’s proprietary connector engine that links external cloud storage systems, like Adobe Experience Manager, Box, Dropbox, Google Drive, or Microsoft OneDrive, directly to Korbyt’s Media Manager. Think of a Courier as an automated delivery service that routinely fetches or removes media assets based on your rules, so your digital signage always reflects the most current content without manual effort.
To configure a Courier, click the button for your service, and you will be prompted to log into the selected service. You can then specify a folder (including all subfolders, if desired) within that service to connect to.
Once connected, you can set the Courier to run every 30 minutes, hourly, or daily. It copies any new items from the cloud service into your Korbyt Media Manager and removes items from Korbyt that have been removed from the DAM. This ensures that only the most up-to-date items are present in Korbyt.
Each Courier rule can also tag everything it imports automatically. A dynamic “Clever Playlist” in Korbyt can then schedule those items to the correct screens automatically, based on the folder they are in or the tags assigned, without any hands-on work in the CMS.
The Korbyt CMS supports multiple Couriers, even multiple Couriers to the same cloud service. Different users can create their own Couriers with their own tagging and folder structures, driving different automated content to the right screens.
Designing in Canva? Finished designs can be published straight to Korbyt from Canva, ready for the same folder and tag-based automation.
2. Microsoft SharePoint Adapter Integration
For organizations using SharePoint as a DAM or content repository, Korbyt provides a dedicated SharePoint Adapter.
This adapter connects to your organization’s Microsoft SharePoint account to access stored files and information, using Microsoft’s ability to share information with trusted applications. It even allows SharePoint to create and manage a Playlist and set date ranges for displaying content.
Korbyt’s advanced adapter templates take the guesswork out of connecting through SharePoint APIs. When configured, these templates pass not only media items but also scheduling information, such as playlists, view duration, and validity dates, from SharePoint to Korbyt. This gives you complete control of content and scheduling through SharePoint, in addition to normal folder and tag-based automation.
For step-by-step setup, see How to set up and use a SharePoint Documents Adapter.
3. URL and HTML-Based Elements
For DAMs that support external publishing via URLs or embeddable HTML, Korbyt’s Layout Builder offers flexible integration, with native elements to display either type of content directly on a screen.
Korbyt’s HTML Element allows any embeddable HTML code to be added to a full display or an area of a display.
Korbyt’s URL Element can display any iframe-capable website in a design, even if that website requires Form-Based or OAuth 2.0 authentication to be reached.
4. Korbyt API: Connect Any DAM
These integrations keep displayed content up to date because Korbyt shows the latest version published on your DAM. No further action required.
Couriers and the SharePoint Adapter cover the most common repositories. Many enterprises, though, run DAM platforms with their own metadata models and approval workflows. For those, the Korbyt API lets your DAM, or a small integration service next to it, push approved assets straight into Korbyt Media Manager. Folders, tags, and validity dates come along with each asset.
How it works
A Korbyt admin creates an API key in the CMS. The integration exchanges that key for an access token and uses Korbyt’s REST endpoints to manage media:
- Add or update media. Upload a new file, or overwrite an existing media item by its ID. Overwriting replaces the file in place, so every playlist already using that item picks up the new version automatically. Each request can set the target folder, tags, copyright information, and start and end validity dates
- Change validity dates without re-uploading. If an asset’s usage rights are extended or cut short in the DAM, one call updates when the asset is allowed to play
- Remove media. When an asset is withdrawn or archived in the DAM, the integration deletes it from Korbyt so it can no longer play
- Check what’s already in Korbyt. List calls filter by folder, tag, file type, and “changed since” date. That makes it easy to reconcile the two systems on a schedule
- Adjust playlist rules. Dynamic playlist tag rules can be updated through the API, and connected players are told to check in right away
Full endpoint details are in the Korbyt API Reference.
Example: from approval to screen with no CMS login
- A brand manager approves a spring campaign graphic in the DAM. They tag it for the Northeast division and set its license to expire May 31
- The DAM’s approval event triggers a lightweight function. This could be an AWS Lambda, an Azure Function, or your integration platform of choice
- The function pulls a screen-ready version of the file (1080p or 4K rather than the print master). It uploads that file into a /DAM/Campaigns folder in Korbyt with the tags “Northeast” and “Spring-Promo” and an end date of May 31
- A Clever Playlist matches content tags to each player’s division metadata. The new graphic starts playing on every Northeast screen
- On May 31 the graphic drops out of rotation on its own. If the campaign is pulled early, the DAM sends a second event, and the function either moves the end date up or deletes the item
- When the design team revises the graphic mid-campaign, the function overwrites the existing item. Screens show the new version without anyone touching a playlist
When to use the API instead of a Courier
- Your DAM isn’t one of the services Couriers support
- You want content to land as soon as it’s approved, not on the next 30-minute, hourly, or daily Courier run
- You need tags and validity dates set asset by asset from DAM metadata like region, audience, campaign, or license expiration. A Courier rule applies the same tags to everything it imports
- You want to send files sized for screens rather than full-resolution masters
Build it securely
- Create a dedicated API key for each integration. API actions are logged in the CMS audit trail against the key that made them, so a dedicated key makes it clear which changes came from the DAM sync
- Store API credentials in a secrets manager, not in scripts or config files, and rotate them on a schedule. Give them the same care as an admin account
- Keep the DAM as the single source of truth. Approvals, expirations, and deletions should flow in one direction, from the DAM to Korbyt
Key Considerations for Successful Automation
To make DAM-driven automation effective in digital signage, plan your content governance and define rules carefully. Decide how your screens will be identified. Go beyond device names to characteristics like location, the department they serve, and anything else that determines what content is appropriate for them to display.
These factors can be set in Korbyt Media Player’s metadata, providing the data points a Playlist uses to decide whether automated content should play on a specific player. For example, if a player has been told it is in the Northeast division, it can be instructed to play content that is tagged for that division, or that the DAM has saved into a specific folder for that division in Korbyt.
Korbyt Player Management includes standard location values, as well as 100 custom-namable data fields, so your player has all the information it needs to show relevant content.
These metadata fields can be referenced in Clever Playlists as variables rather than set values. The example below uses the “City” value to find content tagged with the matching city name, so a single rule programs every city instead of needing a unique rule for each. You can use this same approach with any of a player’s custom-namable data fields.
Risks and Pitfalls to Avoid
Automation offers significant efficiencies, but it’s critical to design your integrations thoughtfully to avoid these common traps:
- Over-reliance on automation without oversight. Automation is powerful, but it still needs governance. A broken tag, disconnected folder, or incorrect rule can cause stale or irrelevant content to persist
- Asset duplication from poor taxonomy design. Without clear file naming conventions or folder structures, teams risk duplicating assets, which leads to storage bloat and brand inconsistency
- Tags that don’t match between systems. If the DAM sends “NE” and the Clever Playlist rule looks for “Northeast,” the content never reaches a screen and nothing flags it. Agree on a shared list of tag values before turning automation on
- Missing expiration dates. Assets without an end date stay in rotation after a campaign or license ends. Map your DAM’s rights or expiration fields to Korbyt validity dates so content retires on schedule
- Gaps in player metadata. Rules that target a division, city, or department skip any player missing that value. Audit player metadata before launch, and include it in the setup checklist for every new screen
- Editing synced content in two places. Manual changes to DAM-synced items inside Korbyt can be overwritten or reversed by the next sync, depending on how the integration is set up. Make changes in the DAM and let them flow to Korbyt
- Performance bottlenecks. High-resolution media that isn’t optimized for screen delivery can slow down content rendering or overwhelm low-bandwidth locations. If you’re using the Korbyt API, send a screen-sized version of each asset rather than the original master
- Security vulnerabilities. If internal DAMs feed public-facing digital signage, appropriate authentication, access control, and API hardening are essential. Treat Korbyt API credentials like admin credentials, use a dedicated key for each integration, and store keys in a secrets manager. See Korbyt Security for more on how we protect the platform
Mitigating these issues requires coordination between IT, communications, and content teams, along with regular audits and ongoing refinement.
Final Thoughts: Unlocking Scalable, Brand-Safe Digital Signage
Integrating your DAM isn’t just about convenience. It’s a catalyst for turning digital signage into a real-time, brand-consistent communication platform.
Here’s what organizations gain:
- Faster publishing cycles with fewer manual handoffs
- Always up-to-date content from a single source of truth
- Consistent visual identity across locations, devices, and departments
- Smarter workflows that scale without increasing headcount
To get started, consider piloting the integration with one content stream, such as HR updates, brand marketing, or location-specific promotions. Once your automation rules and folder structures are proven, expanding to other teams or signage zones becomes seamless.
With the right setup, your DAM can turn static screens into living content networks. Paired with a CMS like Korbyt, it becomes the engine powering fast, brand-safe, and intelligently automated digital signage.
Ready to see Korbyt in action? Book 15 minutes with an expert today.
