Triggers - Created fine, working fine, but can't view existing or delete?

OttoFMS
1

Hi,

I’ve successfully created a Trigger using the new 14.4.1 release, and it’s working fine, but on the main ‘Triggers’ UI, it reports no triggers configured, which makes it hard to then remove these, and it feels like the documentation states that there should be something showing here:

CleanShot 2025-12-29 at 12.31.51@2x
CleanShot 2025-12-29 at 12.31.51@2x4062×1512 337 KB

Am I missing something?

2

did you choose the same file with the triggers? - I thought I read they don’t survive a server reboot.

3

Yep, same file, same auth method. I know the triggers are setup because they’re triggering, and I could also see and remove them using native oData calls in Postman, so I think there’s something up with the OttoFMS interface which is stopping it loading them…

4

they do now survive a server reboot since 22.0.4, not before that
there is a difference between web hooks created with or without the .fmp12 - this tool defaults to adding them

during testing never experienced this @JamesG - but I was only ever specifying using one tool at a time just to make sure nothing wonky happened

If you added the web hook externally there is a chance it will not then show in the Otto interface, think they are storing those details somewhere else… as they worked in the previous version too

5

Thanks John, although now I have even more questions?!
Off the top of my head:

  • What’s the difference between specifying a .fmp12 hook and a non .fmp12 hook?
  • Where is this config stored? In the file itself, or on the server, and how does this persist when doing migrations?
  • Are hooks configured manually (e.g via native oData calls) vs hooks configured through OttoFMS completely incompatible? Or is there some crossover?

For such a potentially powerful feature, the lack of detailed documentation from Claris is a bit frustrating…

6

My understanding is that FileMaker Server is storing these triggers somewhere internally. When you create/retrieve the webhooks from the server it uses the string you pass in as the filename to retrieve/create them, so if you create one with test_file.fmp12, retrieving the triggers for test_file will not return that trigger since it was created using a different string.

The hooks created using OData directly should be compatible with OttoFMS, but OttoFMS is always adding the .fmp12 to OData calls that go through the OData proxy (for consistency), so if you create them outside of OttoFMS without the .fmp12 then they will not appear in OttoFMS.

Triggers with and without the .fmp12 both work, but OttoFMS only shows the ones created with the .fmp12. I’m unsure if there is a good way for OttoFMS to display both, and frankly it feels like The endpoint to get webhooks for a file should return all of them for the file, no matter if the .fmp12 is included or not. I’m unsure if anyone has brought up this discrepancy to Claris or not.

-Kyle

7

Yes, and Clay said his recommendation was to do it without the .fmp12

/Preferences/ClarisWebhooks.json

1 Like