Connectors
DAM connectors
Connect a digital asset management platform.
Connect your DAM and Inverity optimizes your asset library, saving each optimized result as a new version of the asset — your masters stay intact.
Supported platforms
| Platform | What you'll need | Setup guide |
|---|---|---|
| Bynder | Your portal URL + a permanent token | Bynder |
| Cloudinary | Cloud name + API key + API secret | Cloudinary |
| Brandfolder | An API key + your Brandfolder ID | Brandfolder |
| Acquia DAM (Widen) | Your domain + an API token | Acquia DAM |
| Canto | Your domain + an access token | Canto |
| Frontify | Your domain + an API token | Frontify |
Connecting
- Create a token in your DAM. In your DAM's settings, create an API token or key with permission to read and add assets. The connect screen links to the exact place for your platform.
- Paste it into Inverity. Open Connectors, choose your DAM, and enter the details from the table above.
- Choose what to optimize. Select the collections or folders to watch.
How write-back works
DAM masters are treated as permanent. Inverity adds the optimized file as a new version or rendition of the asset rather than overwriting your master. Your version history stays intact and your original remains retrievable.
For Cloudinary, the optimized file replaces the same public ID and Cloudinary keeps the version history — so existing delivery URLs continue to resolve.
See How write-back works for the full detail.
Choosing a profile for a DAM
A DAM usually holds source-of-truth assets that get re-edited and re-exported downstream, which argues for a conservative quality profile. If your DAM is really a delivery library for a website, the opposite applies.
Because profiles are set per connected source, you can connect the same organization's DAM and CMS and treat them differently.
Talk to your DAM administrator first
DAM libraries frequently sit inside a rights-management or approval workflow, and adding versions to assets may have downstream effects your team cares about — on notifications, approval states, or integrations that watch for new versions. Confirm the approach on a test collection before running a full library.
Don't see your DAM?
Contact support — we add connectors based on demand.