Closed ynnoj closed 4 years ago
@notrab The toolkit exposes APIs to capture and action webhooks. If a re-build is triggered from a webhook, then the corresponding Gatsby node will be updated/created (via a GraphQL query) or deleted.
Right now you just need to setup your GraphCMS webhooks without payloads for builds and previews to be triggered. This issue is to address that.
Perhaps at some point we can use the payload from the webhook to update the Gatsby nodes, rather than firing a GraphQL query. However there's manual node work required for that so it's a bit more cumbersome.
Due to some recent changes to GraphCMS webhook payloads, this is no longer an issue.
How does webhooks work currently? What is the required options in GraphCMS webhooks setup for preview/builds?