No. But I think it’s standard practice. The webhook is extremely lite.

My webhook handler takes the webhook information and immediately makes a GET request for entity’s full information. I’m adding that information to an Azure database. I can see what changed by accessing the past records added to the database and comparing them chronologically.

It’s a lot of work if you are interested to see what changed in a contact. I only intend to use the historical data to track time in status for work items. All of my contact updates overwrite existing data and don’t keep track of changes.

Thanks @max .

I need it for one reason. If the name is updated in Karbon, then I want to update the name in QBO.

I guess I can accomplish that by checking in QBO if the name matches. If it doesn't, it should update.

Ah, that makes sense. I ended up implementing a lot of “search for x then add/update/ignore as necessary” sub-routines. It takes a little more processing and setup, but it’s much more robust and corrects itself over time if a webhook doesn’t fire or some other issue causes the data not to flow properly.

One thing I haven’t done yet but that might help with this is to add the Karbon key in XML or JSON to the notes in QBO and use that to search, compare, update, or add.

That is actually what I’m working on now. I created a custom field in QBO and added the Karbon ID to easily search, update, map in Power BI, etc.

I’m curious how that will work. I have not played with the QBO API or Zapier connections very much.

I will let you know once it’s done.