Strapi publish webhook triggers our rebuild, do Croct experiences need a republish too?
Our frontend is static. Strapi publish fires webhook, CI rebuilds, done. Works for years.
Now editors also change variant copy in Croct experiences. Question is whether that needs same treatment. Do I add webhook on Croct side to trigger rebuild? Or does variant content bypass the build entirely?
Docs did not give me clear answer for static setup.
1 answer
No rebuild and no webhook needed on the Croct side. Experiences are published from the Croct dashboard and take effect immediately, without a frontend deploy. Only the variant content is authored in Croct, and it is resolved at request time when the slot is fetched, so it never goes through your build.
Your existing pipeline stays exactly as it is: default content updates flow from Strapi as usual through your app's own fetch and the webhook-triggered rebuild.
One workflow detail worth knowing: experiences have statuses (Draft, Active, Paused, Scheduled, Archived). If an editor pauses an experience, visitors immediately see the default slot content again, which in your case is whatever Strapi content your last build baked in. So pausing is also deploy-free.