Hi,
I have played around a little bit with webhooks the last time, and as far as I can see with the design it is implemented it would not work in a reliable way.
But it may also be that I have misunderstood something, in which case I would ask for clarification.
As per my understanding, when I get a notification, I have to read the event queue to get the event (should be the last one?). That works fine so far, but:
We are working on a mutli-user system. So it maybe, that two users modify the same record at the (nearly) same time, even contrary. Your system will then send out two notifications. That will happen in the following way, from my point of view: storing the record to the database, storing of the event to the event-queue, sending the notification. It is possible, that I get the first notification, then read the event queue, but in the meantime the smartsuite system has already written the second event and sent the second notification. In this case, when I grab the last event off the queue, I will get the one for the second notification!
And this scenario assumes that processing within smartsuite is strictly sequential. Otherwise, the behavior would not be predictable at all.
In my opinion the only way to prevent this behavior would be to include the event id in the notification structure. Furthermore, in this case, it would be nice to have "Get Event" function, like the "Get Webhook" function on the API, to request exactly this event. I assume, that you are, naturally, will not able to guarantee full synchronization, as there is even a lot of network time in whole workflow...
But as stated before, it may also be that I have misunderstood something, in which case I would ask for clarification, and maybe detailing the documentation.
Many thanks,
Wolfgang Stahl