Currently, we have an implementation that will
- Update/Create a contact in HubSpot when a contact is created or updated, in our system
- Update/Create a contact into our system when a contact is created or updated, in HubSpot
Both work well, BUT because we have triggers set up in HubSpot’s webhook to notify us when a change happens, or a contact is created, what we run in to is this:
- We save our changes
- We make the appropriate HubSpot API call
* We would like it to end here, but instead…
- HubSpot’s webhook notifies us of a change (that we just made)
- Our system processes this - redundantly
- At this point our system knows not to bounce back
Is there way to either
1. not have HubSpot webhook send us a notice if we changed something via the API or…
2. identify that the notice coming back to us is tied to the API call we just made, so we avoid running our biz logic
I could totally be missing a piece, so wanted to ask before I got creative and started writing an out of the box solution (probably time stamp tracking or something)
Thanks!
