CMS integrations
Push scene metadata and Shield verdicts straight into the CMS you already run. No catalog migration — Jetwild writes to the records you already have.
CMS integrations aren’t wired up yet — there’s no connector backend, so you can’t connect a CMS today. This page describes the planned outbound sync so you can see the shape ahead of release.
Run only the Shield API and still sync verdicts into your CMS. Scan in Jetwild, write the compliance status onto your record.
Planned CMS connectors
How sync works
The connection is outbound — Jetwild pushes to your CMS; it never reads your catalog back.
- Authenticate once with your CMS endpoint + API token (OAuth where the platform supports it).
- Map Jetwild fields to your schema — title, tags, models, copy, and the Shield verdict.
- Sync — on every scan or scene update, Jetwild pushes the delta to the
matching record, keyed by your
external_id.
Triggers: scene.ready, scene.updated, and shield.cleared / shield.flagged.
Failed pushes retry with backoff and surface in the connection’s sync log.
Per-CMS setup
Each platform authenticates differently. Set up the connection on your side, then connect it here.
Field mapping
Jetwild ships sensible defaults per platform; override any row in the connection settings. The most common map:
Upload sources
Pull masters from wherever they live — Jetwild reads from S3, Bunny, FTP/SFTP, and Google Sheets manifests.