Deployment Webhook

    You can now configure a deployment webhook to be triggered upon successful deployments to any of your Umbraco Cloud environments, e.g. when deploying from your local environment to your Cloud Development environment. Upon a successful deployment general information about the deployment will be posted in a JSON format to the specific url you have configured.

    Use cases

    This can find uses in many 'audit' cases when you would like to let others know about what is happening with your site. Here are some example of cases where this feature could be useful:

    1. Any deployments to the Live site could be relevant for many parties in a company. Posting information about them in internal communication channels like Slack is made possible using this feature.
    2. Monitoring of the whole deployment cycle. A successful deployment might result in a potentially breaking change. Integrating the webhook with other monitoring services, you could easily find out which deployment has caused the issue.
    3. Letting content editors know about particular deployments when a new document type was added as they can now easily use the new document type.

    Configuration steps

    Adding deployment webhook

    1. From the Umbraco Cloud Portal go to Settings -> Manage Webhooks
    2. Select the environment for which to register a webhook
    3. Fill in the url to which the data about a deployment should be posted to. Absolute URL with http/https schema is an acceptable input to the field - ex.
    4. Add Webhook

    Sample data

    General information about the deployment (to the configured environment) will be posted in JSON format to the url (configured in the previous section).


    The headers contains information about the payload in JSON format as well as a version of the payload.

    X-Umb-Webhook-Version: 1
    Content-Type: application/json; charset=utf-8


    Contents of the payload contain general information about the current deployment with links to the project in the Portal and the frontend of the environment. Last part of the contents is a collection/enumeration of commits that were deployed to the environment, mentioning the author, the commit message and changed files.

        "Author":"Laughing Unicorn",
        "Message":"Adding document type 'LaughingUnicornLaughs'",
                "AuthorName":"Laughing Unicorn",
                "Message":"Adding document-type 'LaughingUnicornLaughs'\n",
                "AuthorName":"Laughing Unicorn",
                "Message":"Adding template 'LaughingUnicornLaughs'\n",