There’s another aspect of this that’s super important, I haven’t been able to complete a full test yet, but this is what I suspect to be the case. If anyone out there is using developer webhooks and has more information to add, that would be great but in the meantime, I will try to test this out fully over the weekend.
As per my comment above, calculation fields produce webhooks. The other day, I was playing around with a dashboard app based on one of my apps that have webhooks instead. I created a report widget for this app, played around with it for a bit, and then deleted it. Later on, I realized that I had hit the API rate limit for this app. Items in this app were being updated when I had not done anything to them at all. After more investigation, when I tried to inspect the revision history, I saw the following message:
{
"status_code": 404,
"endpoint": "/v1/record/107923835/revision/previous/4",
"error_code": "not_found",
"error_message": "getFieldsByIdsOrFail: Fields with IDs 481779 not found!"
}
I haven’t been able to confirm yet, but what I believe is the case is that the Dashboarding tool is actually creating calculation fields within that app for its own purposes. And as we have determined, calculation fields produce webhooks.
(EDIT: I’m most likely wrong here, this was my initial gut reaction, please ignore my comments regarding calcs)
There really should be some way to shut this off, otherwise, anyone wishing to build an integration on top of Tape with apps that are using Dashboards are going to be constantly overwhelmed with hooks.
Again, if anyone can add more right now, that would be awesome, otherwise I just need to do some testing at a time when the system is relatively quiet.
@Tim