Add a Webhook to fix Generator Issues
6 repliesLast updated: Aug 3, 2020
I'm having issues with both Sanity's Eleventy generator as well as their Gridsome generator. New published posts added to Studio are not being displayed on the front end. I thought maybe the problem was me. So, I tried Sanity's Nuxt generator, and that works as advertised. Has anyone had the same experience?
BTW, my local environment doesn't have this issue. I can see all my updated posts locally. But, none of this helps me if I can't see these posts/changes on my remote site. And then I thought maybe the issue was with Netlify. But, all I see is 2 deploy builds since 2 days ago regarding template changes, not content changes.
Hi Scott, whether your front-end deploys automatically on content changes in Sanity depends on if you have a webhook set up for this.
For more information on webhooks:
https://www.sanity.io/docs/webhooks
To set up a webhook, enter your project on
manage.sanity.io and go to Settings > API > Webhooks > Add new webhook. If you point this to a Netlify build endpoint (or a custom function if you prefer), it should automatically trigger builds.
Bear in mind that this can easily use up your build minutes on Netlify if you publish content frequently. As an alternative, you might want to consider manually triggering a deploy hook instead whenever you finish editing and want to publish changes to your front-end. There is a Netlify widget for the Studio that allows you to do just that from the Dashboard:
https://www.npmjs.com/package/sanity-plugin-dashboard-widget-netlify 🙂
For more information on webhooks:
https://www.sanity.io/docs/webhooks
To set up a webhook, enter your project on
manage.sanity.io and go to Settings > API > Webhooks > Add new webhook. If you point this to a Netlify build endpoint (or a custom function if you prefer), it should automatically trigger builds.
Bear in mind that this can easily use up your build minutes on Netlify if you publish content frequently. As an alternative, you might want to consider manually triggering a deploy hook instead whenever you finish editing and want to publish changes to your front-end. There is a Netlify widget for the Studio that allows you to do just that from the Dashboard:
https://www.npmjs.com/package/sanity-plugin-dashboard-widget-netlify 🙂
Hi Scott, whether your front-end deploys automatically on content changes in Sanity depends on if you have a webhook set up for this.
For more information on webhooks:
https://www.sanity.io/docs/webhooks
To set up a webhook, enter your project on
manage.sanity.io and go to Settings > API > Webhooks > Add new webhook. If you point this to a Netlify build endpoint (or a custom function if you prefer), it should automatically trigger builds.
Bear in mind that this can easily use up your build minutes on Netlify if you publish content frequently. As an alternative, you might want to consider manually triggering a deploy hook instead whenever you finish editing and want to publish changes to your front-end. There is a Netlify widget for the Studio that allows you to do just that from the Dashboard:
https://www.npmjs.com/package/sanity-plugin-dashboard-widget-netlify 🙂
For more information on webhooks:
https://www.sanity.io/docs/webhooks
To set up a webhook, enter your project on
manage.sanity.io and go to Settings > API > Webhooks > Add new webhook. If you point this to a Netlify build endpoint (or a custom function if you prefer), it should automatically trigger builds.
Bear in mind that this can easily use up your build minutes on Netlify if you publish content frequently. As an alternative, you might want to consider manually triggering a deploy hook instead whenever you finish editing and want to publish changes to your front-end. There is a Netlify widget for the Studio that allows you to do just that from the Dashboard:
https://www.npmjs.com/package/sanity-plugin-dashboard-widget-netlify 🙂
Thanks user M I see that explanation now. Plus, that explains why my Netlify dashboard widget in Studio is broken. It probably needs to be configured yet.
Sorry about that Scott, it’s an issue we’re resolving at the moment to make it set up the widget automatically. Let me know if you need any pointers while configuring. Also, there’s this thread to reference: https://sanity-io-land.slack.com/archives/C9Z7RC3V1/p1595526846041300
Great! That's very helpful user M
Was this answer helpful?
Sanity – Build the way you think, not the way your CMS thinks
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.
