When preparing content with Scrivito, the most relevant action is the final publishing of the working copy. Not only is this the moment in which your work result is presented to the public, you are now also given the opportunity to call any web services of your choice. For this, Scrivito lets you define up to ten webhooks for each CMS. You can use them to subsequently perform technical actions such as having Google update its index, start the prerendering process to make your single-page app accessible to crawlers, etc. If you would like to always drop someone a note after publishing, or post a message to a Slack channel – Scrivito’s publish webhooks are great for performing all the tasks needed to round off each and every update to your website content.

Setting up a webhook is as easy as copy/pasting the web service URL to an input box. Just open the website settings page in your dashboard and click “Edit” in the “Publish Webhooks” section.

You can secure your web services against unauthorized use by specifying a secret token and validating it in the web service. See the webhooks documentation for further details and examples.

When the webhook URLs are posted, metadata about the publishing action, e.g. the CMS tenant ID, the user ID, and the list of the changed CMS objects, is sent to the web service, allowing you to take appropriate action based on these details. For example, when notifying someone via a web service, you might only want to act on changes to content relevant to the recipient.

In case you are in need of inspiration on which platform to use for your web services, take a look at our articles related to this topic, e.g. Posting Form Content to a Slack Channel via an AWS Lambda Function or Using an AWS Lambda Function to Send an Email after Form Submission.