Data going into incorrect repository

[MattPallatt]

I have a free HubSpot account. I have a client with a paid HubSpot Account. I have an integration with my CMS which is pushing data, through the V3 Forms API INTO the clients paid hubspot account. When this happens I get an email from MY HubSpot account telling me that data has gone into my HubSpot account too. So it's ending up in both accounts. I have validated in code that we are not sending data from our CMS website into my HubSpot, so where would I look in HubSpot to understand if there are any webhooks etc. configured that would be doing the above, because I currently think I've gone insane. 

[SteveHTM]

@MattPallatt - how would you be able to "push", for example,  contact data through an API call if it wasn't in an originating CRM record?

Or am I completely on the wrong track?

Steve

[MattPallatt]

so I'm not a hubspot expect _at all_ so I'm perhaps going at this the wrong way, but my understanding is that to trigger workflow etc. on submissions we need to pushing data through the forms API as opposed to directly using the contacts API - so we're using https://legacydocs.hubspot.com/docs/methods/forms/submit_form to push data through a form and into CRM. I can see no settings on the form which would indicate why what is happening is in fact happening. But I seemingly have two copies of data.

[SteveHTM]

I've never used this older API - but from the writeup the data push is unauthenticated.

Which portal ID are you using in the JS code? If it's the paid (client) instance, then I'm not sure I understand the role of the "free" instance in this setup?

Just an unrelated FYI related to workflow triggers - a change in contact data or a new contact can trigger a workflow just fine  (presuming that the paid instance has workflow automation as a feature). But then you woudl need to be using an authenticated API call from one instance to the other - which is what I assumed in my original response. 

Steve

[MattPallatt]

Sorry Steve, yes, am using the authenticated endpoint.

And the free instance really has no place in the setup - that's in essence my problem. It was set up to develop against, but now we've swapped to the client instance it shouldn't be in the scope of the solution - and yet, I get a record into my free CRM whenever a form is submitted.