https://community.hubspot.com/t5/APIs-Integrations/Hubspot-Addon-to-many-request-based-on-form-submission/m-p/359675#M35369 <P>Hi&nbsp;<a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/66274">@WendyGoh</a>,</P><P>&nbsp;</P><P>Thank you for the reply!&nbsp;</P><P>Sorry if I was not clear on my post. Let's clarify:</P><P>1. Observing the "Monitor" tool at the Hubspot app interface, I'm receiving only the 3 requests. In theory, it's the expected result when a new contact is created. Considering that the two others properties of the scope has been fullfill by the user.</P><P>&nbsp;</P><P>Observing again my app, I'm realising that, in some cases, a "race condition" may happening. I need to fix this!</P><P>&nbsp;</P><P>But the main reason that I'm posting here is that, every test that I made creating new contacts, clicking only once on the submit button, the result in Hubspot was the expected one. But every new contact created by clicking more than once on the submit button, duplicates or triplicates the associanted deal. Dispite the fact that the monitor tool always shows only the 3 requests.</P><P>&nbsp;</P><P>2. There are layers that determine when create or update the deal. This application in specific doesn't have a data base to store the Hubspot data. I'll try to synthetize the process:</P><P>a) For each index of the Hubspot request array, the app gets the "objectId" and consume the Hubspot API (V3) to get the contact information, using the method "Read".&nbsp;&nbsp;</P><P>b) If the contact exists, the app checks if the properties that is need exists. If exists, the process goes on, otherwise returns false.</P><P>c) If the conditions is satisfied, the API is consumed again, to check if there a deal associated with this contact object.</P><P>d) If the contact doesn't have any associeted deal object, the API is consumed again to create a new deal object,&nbsp; and than consumed again to associate this new deal to the contact.</P><P>e) If there is already a deal or deals associated, the API is consumed again to get every deal informations, from the associated deal or deals.</P><P>f) The app checks if any of those deals matches&nbsp;with the requested data. If match, the deal is updated, otherwise a new deal is created.</P><P>&nbsp;</P><P>That is how the plugin works. I don't know if I'm doing something wrong, but that's how I managed to make it work.</P><P>I hope it clarifies.</P><P>&nbsp;</P><P>Thanks,&nbsp;&nbsp;</P> Wed, 05 Aug 2020 14:55:47 GMT hilton22 2020-08-05T14:55:47Z