Troubleshooting your ArcGIS Connector for Power Automate Triggers with Webhook.site
There are times when your Power Automate flow might not be running as expected, but how do you determine what the source of the issue is? It is tough when integrating multiple systems and applications together, and it can be common to think the issue is with the Power Automate trigger, as that is where the issue is surfacing. But often the issue is further upstream and surfacing because the webhook is not firing. But how can you tell?
A tool I use when troubleshooting is Webhook.site. This utility allows you to generate unique URL listeners to notify you that a webhook is sending a payload as expected. It is quick to get started and can easily let you know if your feature layers are initiating a webhook.
Webhook.site is a utility to use for basic debugging. With a free account, you can generate unique URLs to test whether the webhook is firing. This will help you to determine if the webhook is working as expected or if the issue is with the Power Automate flow.
Getting Started
After setting up your Webhook.site profile (or using the free capability), they will provide you with a URL, an email address, as well as DNS and proxy CLI resources. In this scenario for testing feature service webhooks – we will be using the ‘Your unique URL.’
Setting up the Test
Now that you have the URL, we need to attach it to the feature layer to test whether the webhook is firing or not. Start on the item details page scroll to the service URL and click the ‘View’ icon.
From the Services Directory page, click the ‘Admin’ link in the top right corner.
On the Admin page, click the ‘WebHooks’ link.
From the webhook page you’ll see all the webhooks associated with the feature service. To begin our testing and troubleshooting, we will need to create a new webhook with the URL provided from Webhook.site. This will help us to test whether the webhook is firing or if there is a problem in the Power Automate flow. Check the Webhooks documentation for a description and example usage of creating a webhook manually. When it is created your page will look similar to the image below.
With this wired up, you can now begin testing to see if the webhooks are firing. When the appropriate event is done against the feature service, the page will show that the webhook has fired and is working as expected.
Hopefully this tool and the steps outlined here will help you to better troubleshoot and understand the source of issues when using webhooks as triggers in your Power Automate flows.