こんにちは、カスタムプリントサービスが時々失敗したりタイムアウトしたりしていて、その頻度を把握したいと思い、ツールが実行されるとメールで通知するWebhookを設定してみようと考えました。私は地方自治体でPower Automate、Enterprise 11.5を使っています。Survey123の回答に基づくPAフローはいくつか成功裏に設定しましたが、基本的に他のワークフローではこのツールにまだあまり慣れていません。私の理解では、このタスクは「When a HTTP request is received」トリガーを使って始めるべきだと思います。それを設定し、次にURLを生成する2番目のステップを追加しました。その後、そのURLをブラウザとGP serviceを実行しているサーバーサイトでテストすると、次のメッセージが表示されます: {"error":{"code":"TriggerRequestMethodNotValid","message":"このリクエストのHTTPメソッドは無効です: 期待されるのは 'POST' ですが、実際は 'GET' です。","messageTemplate":"TriggerRequestMethodNotValid"}} 以前の投稿から判断すると、これは正常な応答だと思います。次にサーバー管理画面に移動してWebhookを作成しようとします: しかし、次の応答が返ってきます: 'エラー Webhookの作成または更新ができません。URLにアクセスできません: ' PAはまだ初心者なので、どんな助けでも感謝します！

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

GP ServiceのWebhook - エラー: Webhookの作成または更新ができません。URLにアクセスできません

ZachBodenner

こんにちは、 <\/P>

カスタムプリントサービスが時々失敗したりタイムアウトしたりしていて、その頻度を把握したいと思い、ツールが実行されるとメールで通知するWebhookを設定してみようと考えました。私は地方自治体でPower Automate、Enterprise 11.5を使っています。Survey123の回答に基づくPAフローはいくつか成功裏に設定しましたが、基本的に他のワークフローではこのツールにまだあまり慣れていません。私の理解では、このタスクは「When a HTTP request is received」トリガーを使って始めるべきだと思います。それを設定し、次にURLを生成する2番目のステップを追加しました。<\/P>

<\/span><\/P>その後、そのURLをブラウザとGP serviceを実行しているサーバーサイトでテストすると、次のメッセージが表示されます:<\/P>{"error":{"code":"TriggerRequestMethodNotValid","message":"このリクエストのHTTPメソッドは無効です: 期待されるのは 'POST' ですが、実際は 'GET' です。","messageTemplate":"TriggerRequestMethodNotValid"}}<\/PRE>以前の投稿から判断すると、これは正常な応答だと思います。<\/P>次にサーバー管理画面に移動してWebhookを作成しようとします:<\/P><\/span><\/P> <\/P>しかし、次の応答が返ってきます: 'エラー <\/I><\/FONT>Webhookの作成または更新ができません。URLにアクセスできません: <PAからのPOST URL>'<\/FONT><\/P>PAはまだ初心者なので、どんな助けでも感謝します！<\/FONT><\/P>

タグ付きの投稿をもっと見る

Accepted answers

OlaIHamed

Hi Zach,

The response you're getting when browsing to the Power Automate URL is actually a good sign. The message:
The HTTP method for this request is not valid: expected 'POST' and actual 'GET'
simply indicates that the endpoint is reachable and that Power Automate is listening, it just expects a POST request rather than a GET request.

The "URL is not reachable" error from ArcGIS Server typically means that during webhook creation, ArcGIS Server is unable to successfully validate or connect to the endpoint.

One common cause in on-premises ArcGIS Enterprise deployments is that the ArcGIS Server machine cannot establish an outbound HTTPS connection to the Power Automate endpoint. This may be due to a firewall, proxy configuration, SSL inspection, or outbound internet restrictions.

To help narrow it down, I'd recommend testing the connection directly from the ArcGIS Server machine using PowerShell:
Invoke-RestMethod `
-Uri "YOUR_POWER_AUTOMATE_URL" `
-Method POST `
-Body '{"test": true}' `
-ContentType "application/json"

This sends a POST request from the ArcGIS Server machine, similar to what ArcGIS Server does when firing a webhook.

What to expect:

If the request succeeds (for example, you receive a 200 or 202 response and your Power Automate flow is triggered), then the network path is working correctly and the issue is likely elsewhere.
If you receive a timeout or connection error, then the ArcGIS Server machine is likely unable to reach the Power Automate endpoint. In that case, it would be worth checking with your IT team whether outbound HTTPS (port 443), proxy settings, or access to the required Microsoft endpoints is being restricted.

In our environment, we encountered a similar challenge and ultimately hosted a small webhook receiver locally (a lightweight Python API behind IIS). That approach worked well because it kept all webhook traffic within our internal network and avoided dependencies on outbound internet connectivity. While that may not be necessary in your case, it's another option if external connectivity becomes a limiting factor.

I hope this helps! I'd be interested to hear what the PowerShell test returns, as that should give a much clearer indication of where the issue lies.

Kind regards,

Ola

All comments

danielri

Usually there is a middle-ware that handles the payload, I don't think you can go directly to from Survey123 or FieldMaps to ArcGIS Server?

Paste the payload URL provided by your external webhook service (e.g., Power Automate, Make, Zapier) into the field.

OlaIHamed

Hi Zach,

What to expect:

If the request succeeds (for example, you receive a 200 or 202 response and your Power Automate flow is triggered), then the network path is working correctly and the issue is likely elsewhere.
If you receive a timeout or connection error, then the ArcGIS Server machine is likely unable to reach the Power Automate endpoint. In that case, it would be worth checking with your IT team whether outbound HTTPS (port 443), proxy settings, or access to the required Microsoft endpoints is being restricted.

I hope this helps! I'd be interested to hear what the PowerShell test returns, as that should give a much clearer indication of where the issue lies.

Kind regards,

Ola

ZachBodenner

Thanks for the detailed response! So I ran the powershell command and I got an error that began: Invoke-RestMethod : {"error":{"code":"DirectApiAuthorizationRequired","message":"The OAuth authorization scheme is
required. Please add authentication scheme and try again."}}

So it turns out my issue was not so complicated as all that: I actually just had to change my authorized triggerer from anyone in my org, to just, anyone:

Now I'm not done with the whole thing yet, so I might have another question, but for now I'll mark your response as a solution!

OlaIHamed

Glad you got it working, Zach!

That makes sense. The "Anyone in my organization" trigger requires Microsoft Entra ID authentication, which ArcGIS Server doesn't provide when sending webhook requests. Changing it to "Anyone" is the right approach.

One thing to keep in mind: with the trigger set to "Anyone", the endpoint is publicly accessible. The URL itself is long and random, so it's unlikely someone would guess it, but if you want an extra layer of security,
you could configure a Signature Key/Secret when creating the webhook and validating it in your Power Automate flow for an extra layer of security.

Thanks for following up with the solution. It'll definitely help the next person who runs into the same issue.

Happy mapping!
Ola

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.