idea Provide Webhook Logging in ArcGIS Survey123 Ideas

Provide Webhook Logging

Andrew-Bowne — Wed, 19 May 2021 16:52:37 GMT

Please provide some sort of logging for payloads being sent to a webhook. There have been instances where a payload was never received by Integromat. It would be nice to see some sort of logging when a payload is successfully sent and if it is successfully received.

Re: Provide Webhook Logging

KeithOlsen — Wed, 19 May 2021 16:58:01 GMT

Yes please! We need at the very least a log of webhook triggers. I would also like a way to retrigger the webhook if it fails so I can get the data moving where it needs to go. Sometimes the payload doesn't show up in Integromat at all (history or incomplete executions). Thanks!

Re: Provide Webhook Logging

TylerBragg2 — Mon, 14 Jun 2021 18:12:27 GMT

I agree with this. I've had several issues with Survey123 not sending webhook triggers to Integromat, and I've been trying to find a way to check a log. I'm guessing there isn't one. If not, there should be a way to check that. I'm sure it's logged somewhere.

Re: Provide Webhook Logging

StrathconaBTS — Tue, 21 Sep 2021 17:14:33 GMT

I would love to be able to audit webhooks. We have surveys being submitted by an employee using a Mac submitting the survey via the web browser which never triggers the webhook which is causing significant inefficiencies. We are using a paid subscription of Integromat.

Re: Provide Webhook Logging

JulieMikolajczyk — Thu, 07 Oct 2021 23:59:37 GMT

This log would be very appreciated. It is very challenging when there is an issue with this part of the workflow because Esri says to talk to Integromat and they say to talk to Esri. This would hopefully help us pinpoint where the error actually originates.

Re: Provide Webhook Logging

StrathconaBTS — Tue, 12 Apr 2022 16:06:10 GMT

Definitely needed with the flakey behaviour of this integration. I've actually had to write an entire new integration to check for missed webhooks because it happens so often!

Re: Provide Webhook Logging

RobertAnderson3 — Thu, 11 May 2023 14:33:39 GMT

Got here from a forum post about webhooks randomly not triggering at all, showing no history of the submission from Survey123.

While I think the core of the issue needs to be addressed by Esri running some checks to make sure the trigger has been sent to the webhook, adding a log for us to review to see if we can find some commonalities so we can instruct our users to avoid certain behaviours would be very helpful.

Re: Provide Webhook Logging

EOS_GeospatialTeam — Wed, 04 Sep 2024 22:26:02 GMT

Had a webhook fail to deliver any payload to the FME Flow webhook it has happily provided JSON to or months, but no S123 logs to check, so can't be certain what happened. At least the webhook triggered so we knew a survey response was submitted, so not the end of the world as long as it doesn't keep happening.

So yes, logs would be very useful.

Re: Provide Webhook Logging

MarlboroughDistrict_Council — Thu, 31 Oct 2024 19:08:40 GMT

How this isn't a thing already is baffling. I had a situation yesterday where a new Survey123 report was made but for some reason my FME Server process didn't run as the webhook wasn't triggered. I can't tell if S123 sent anything or not...? There's nothing in the FME logs so I can only assume the issue was on the S123 side?

Re: Provide Webhook Logging

Rob-RBG — Wed, 14 May 2025 07:54:01 GMT

Monitoring, flagging and allowing a user to re-try if a HTTP 2xx success code is not received is really important as due to the webhook being sent from the device rather than the server there is no way of centrally investigating the success of a webhook submission. The send is managed for the submission to the feature service so it is the same functionality required for the webhook. An alternative approach would be submitting the webhook before submitting the survey and then recording in the survey feature service submission whether the webhook had a success code returned to allow for monitoring, investigation and management.