Select to view content in your preferred language

Notebook Server 11.5 Webhook Receivers

95
1
a week ago
Labels (1)
Justin_Greco
Frequent Contributor

I noticed that in the release notes for 11.5 there is now the ability to set up a webhook receiver.  The documentation is very limited.  It gives you instructions for creating the receiver, which includes specifying the notebook you want the webhook to trigger, a secret (which I think can just be random 32 digit string), an API token (which I assumes means I need to generate a token on Portal and include that) and signature headers (documentation has "x-esrihook-signature,x-hub-signature-256" as an example.  This gives me a webhook URL.

I took that webhook URL and used it to set up a webhook on a feature layer (does have edit tracking enabled) and set it to FeatureCreated.  My expectation is that the notebook would run after I created a feature, which I don't have any evidence that it ran.

Since the documentation is limited, I am thinking something is not configured correctly either when creating the webhook receiver or with the URL I am setting on the feature service webhook.  Is anyone aware of any additional documentation or blog posts about this feature?

 

0 Kudos
1 Reply
KevinHibma
Esri Regular Contributor

Thanks, Justin, we'll use your question as a motivator to get more information out.

For your issue. A few things to try:

  1. You can setup a second webhook with the exact same parameters as your Notebook Webhook Receiver, just point it some place else, like https://webhook.site/  - This should give an idea if it's working
  2. Alternatively, ArcGIS Server debug logs should show if the webhook is being dispatched, or if there are errors
  3. Finally, if you set debug logs in the Notebook Server Administrator, you should see logging related to the notebook triggering.

For the most part, setting up the receiver is the bulk of the work. The only thing you didn't note was the webhook secret key. Did you use the matching 32 character secret key while creating the webhook? This same value must be set when creating the webhook.

0 Kudos