I missed your reply and just responding now. If you read further up the thread, there was a recommendation against webhooks for long running processes. Dato just about has all the right features, it’s just missing support for draft vs publish in build triggers.
Build triggers are exactly what we need because they are decoupled and asynchronous (compared to straight up webhooks). This means we can take as long as we want to build the site (although typically a site build is around 8 seconds) and callback to Dato upon completion with the status.
However, there’s no point in building the site for published items if our content editors cannot see their changes in draft mode. What we are hoping for is to be able to trigger a build from either the save or the publish action. For save triggers, we will build and redeploy our stage environment and for publish triggers, build and redeploy production.
Can this be achieved today? If not, is it on the roadmap?