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; } } }

Webhook sur le service GP - Erreur : Impossible de créer ou de mettre à jour le webhook. L'URL n'est pas accessible

ZachBodenner

Bonjour, <\/P>

J'ai des difficultés avec un service d'impression personnalisé qui échoue ou expire occasionnellement et je veux comprendre à quelle fréquence cela se produit, alors j'ai pensé essayer de configurer un webhook pour m'envoyer un e-mail lorsque l'outil s'exécute. Je travaille dans le gouvernement local sur Power Automate, Enterprise 11.5. J'ai réussi à configurer quelques flux PA basés sur les réponses Survey123, mais je ne suis toujours pas très à l'aise avec cet outil pour pratiquement tout autre flux de travail. D'après ce que je comprends, je devrais commencer cette tâche en utilisant le déclencheur 'When a HTTP request is received'. Je l'ai fait, et ajouté une deuxième étape pour générer l'URL.<\/P>

<\/span><\/P>Je teste ensuite cette URL dans mon navigateur et depuis le site du serveur exécutant le service GP et j'obtiens ce message :<\/P>{"error":{"code":"TriggerRequestMethodNotValid","message":"La méthode HTTP pour cette requête n'est pas valide : attendu 'POST' et reçu 'GET'.","messageTemplate":"TriggerRequestMethodNotValid"}}<\/PRE>Ce qui, d'après des messages précédents, est une réponse correcte ?<\/P>Puis je vais sur l'administration de mon serveur et tente de créer le webhook :<\/P><\/span><\/P> <\/P>Mais je reçois la réponse : 'Erreur <\/I><\/FONT>Impossible de créer ou de mettre à jour le webhook. L'URL n'est pas accessible : <POST URL from PA>'<\/FONT><\/P>Encore novice avec PA, donc toute aide est appréciée !<\/FONT><\/P>

Trouver plus de publications taguées avec

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

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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