Updated Contact Properties Webhook

Hi there,
I’m trying to integerate our system with HS. And we would like to have a two-way-data-stream in the Contacts object and sync updates ever happen to an object between our system and in HS. I managed to accomplish pretty much everything. But, I have a problem in updating our system’s users if a contact has been updated in HS. I tried to look up the workflows and setup a trigger to send a request to our server. But I could not find a trigger that works on property change of the contact.
However, I had a workaround I wanted to try which is trigger the workflow on the “Last Modified Date” using “is less than” with value of 1 day ago. But, the workflow will never re-enroll the contacts since it says in the re-enrollment panel that the re-enrollment might only happen when using “Date” and trigger of “equal to”
And I don’t want to use the recently updated/created API since it would be too complex for such an easy task.
I hope we can find out a way to accomplish this in a reasonable way.
Sincerely,

The “is known” trigger filter will trigger and reenroll each time a property changes. Is that what you need?

The thing is the “is known” filter will trigger the workflow also on creation (not update only)
And if you delete the value of any property and save that the workflow will not be trigger (Because basically it’s “unknown”)

Seems like you could do a trigger on is known OR is unknown, that doesn’t really work well though if you are looking at more than a small handful of properties. But you don’t want to do anything upon creation?

Have you looked into using webhooks where HubSpot can post to a URL of your choosing whenever any data changes? Wouldn’t require workflows or anything like that.

Yeah I did look at the Webhooks API. But, doesn’t that work for Developers account and in order to link it to our standard HS account I do need to list it in Marketplace and then integerate it with our app?

I kinda managed to get it working with the worfklow (is known) but the major problem is that it is being triggered on creation as well which means it will be triggered on import and image you import 10k records that will result in sending huge amount of requests to the server real quick

Have you figured out how to not trigger on creation? I also only want the trigger on modification. Thanks.