Getting started
Connect a source
Link your CMS or DAM so Inverity can optimize your library.
Inverity optimizes media that lives in your existing systems. Connect a source once and Inverity can read your assets, optimize them, and write the results back.
Two ways to connect
One-click sign-in (OAuth). HubSpot, Webflow, and Contentful use a secure sign-in flow. You click through to your platform, approve access, and you're done — there's nothing to copy or store. Shopify is similar, but you install Inverity as an embedded app from your store admin.
Paste a token. Everything else — Sanity, Storyblok, WordPress, Adobe Commerce, BigCommerce, and every DAM — works by creating an API token in your platform and pasting it into Inverity. The connect screen links to the exact place to create it for your platform.
Neither method is more secure than the other in practice: tokens you paste are stored encrypted and used only to reach the assets you point Inverity at. See Tokens and permissions.
Connect
- Open Connectors. In the dashboard, go to Connectors and choose your platform.
- Authorize Inverity. For OAuth platforms, sign in and approve access. For token platforms, follow the on-screen steps to create a token in your platform and paste it, along with any domain or account identifier the screen asks for.
- Pick what to watch. Choose the folders, collections, or products you want optimized. New media there is optimized automatically.
Supported platforms
- Content management: HubSpot, Shopify, Webflow, Contentful, Sanity, Storyblok, WordPress, Adobe Commerce, BigCommerce — see CMS connectors
- Digital asset management: Bynder, Cloudinary, Brandfolder, Acquia DAM (Widen), Canto, Frontify — see DAM connectors
Each platform has its own setup guide with the exact fields it asks for.
Connecting more than one source
A workspace can hold several connected sources at once — for example a Contentful space for your marketing site and a Bynder portal for brand assets. They share the same monthly volume budget, and each can have its own quality profile.
Connect with a service account, not your personal login
Where your platform supports it, create the token under a service or integration user rather than a named person's account. If that person leaves and their access is revoked, your connector doesn't break with them.
Common problems
- "Token is invalid" — the token was mistyped, has expired, or lacks permission to read and add assets.
- "Domain not found" — for domain-based DAMs, the portal URL must match exactly what appears in your platform.
- Connected, but nothing happens — you probably haven't selected any folders to watch yet.
See Connector errors for fixes.