Feature: Default values for Webhook Triggers

[mikewells]

It would be handy for Advanced -> Webhook Trigger to use preset configurable defaults when creating a new certificate.

Alternatively, a way to bulk apply Webhook Triggers to existing certificates.

Context: We have the same action for all certificates (a slack post webhook) and currently have to copy/paste these from other managed sites.

[webprofusion-chrisc]

Thanks Mike, great idea. You're actually the first person I've spoken to thats used the webhooks feature, which probably means that it's been working Ok otherwise!

There's a lot still needs to be done for the 4.x beta but I reckon this could happen during the 4.x timeline.

[mikewells]

Alternatively, how about general app-wide scripting settings that allow for scripts and/or webhooks to be set to run after all renewals?

For people like me who have identical scripts and hooks in all cases.

[nyulawbrian]

However this is implemented, it should be possible to apply different actions (e.g. URL, Method, ContentType, Body) for each Webhook Trigger type. Currently only one Webhook Trigger type and action can be selected.

For example:
In my environment, we use the Webhook to post a notification to Slack (same as OP). I want to customize the message posted based on success or error - change color, message content, throw in a 'danger will robinson' or what-have-you.

There should be the option to apply application-wide or on a per site basis.

[webprofusion-chrisc]

I'm currently working on a new deployment tasks framework for Certify which will allow any number of custom actions and predefined common tasks to be run on cert renewal. I think webhook will become one of these tasks types, then we can look at making it more sophisticated after that. Note that you can currently use post-request powershell scripting to do anything you want (and you can select the same shared powershell script) so if you need more oprtions for posting to webhook etc you could do it in powershell without too much effort. There's not currently a 'run this for every renewal' option and if there was we'd probably need an exclusions list as well (i.e. run it for everything but not these)

[webprofusion-chrisc]

Update: webhooks have been moved to Deployment Tasks in v5, there is currently still no global option though,