Skip to main content
Question

Webhook Automation not writing payload to logs after successful triggering

  • July 10, 2026
  • 2 replies
  • 43 views

eanolan2024
Contributor
Forum|alt.badge.img+2

I created a webhook automation in FME Flow (2025.1.3.3). It is a simple layout the webhook and a action to log a message. 

I connected this webhook in ArcGIS Portal (11.5) under organization → webhooks → Organization webhooks → For /groups -> linked to the webhook API in FME FLOW. This was all pretty simple and easy to do. 

I am able to trigger the automation successfully by making changes to a group. The trigger is logged in the _ fmeautomations.log. I can clearly see the successful triggering --

(Fri-10-Jul-2026 09:35:24.906 AM | INFORM | pool-6-thread-1 | Automation_Webhook (7d4efa47-4a28-4564-928a-c3744e704560) | no-event | 410160 : (Automations) Automation successfully triggered)

However, as shown in this article https://support.safe.com/hc/en-us/articles/25407612807821-Automate-ArcGIS-Enterprise-Portal-Administration-with-Organization-Webhooks-and-FME-Flow

The expected Payload does not follow the “Automation successfully triggered” entry. I can’t find the payload anywhere.

Now, when I turn the automation to debug, I can clearly see the payload after triggering the automation with a group update --

 

2026-07-10T13:36:43.763Z | 410160 : (Automations) Automation successfully triggered
2026-07-10T13:36:43.787Z | Events:[{"source":"group","id":"2783147fefc04eb88e6f83266dd75db2","userId":"60699a79d7fb4fc89ff5d46c2b315d1b","when":1783690603628,"operation":"update","properties":{},"username":"username"}]
Info:{"webhookId":"e3f22f131e0f42aea2fec6b5217b2b71","portalURL":"urlremoved","webhookName":"Payload_Group_Activity","when":1783690603631}

 

Any ideas on why the payload is not writing out to the _ fmeautomations.log?

2 replies

hkingsbury
Celebrity
Forum|alt.badge.img+73
  • Celebrity
  • July 12, 2026

Interesting, I’ve never looked at the automations log to see the payload, I’ve always set up a logger in the workspace that receives the payload.

I guess my reasoning for that approach is that I’ve come across other situations where payloads are logged with escape characters and that makes it difficult to develop the subsequent parsing steps. I prefer to log the data as close to the processing point as possible.

I would assume that the payload is flagged as a debug log type, hence it only getting displayed in the debug logs


zoe.forbes
Safer
Forum|alt.badge.img+10
  • Safer
  • July 15, 2026

Hi ​@eanolan2024,

The fmeautomations.log contains high-level automations information, skipping a lot of detail. For more granular automations logging, check the log associated with the relevant action/trigger. In this instance, action_fmelogaction.log is where you’ll find the payload.

Automations debug logging combines all logging from a particular automation, so here you see entries from fmeautomations.log and action_fmelogaction.log in one place. 

I believe the screenshot you mentioned shows a log equivalent to the debug log in 2025.1. I’ll update the article to make this clearer. Hopefully this answers your question!