I think you’ve figured it out. HelloSign unfortunately does not
differentiate between test requests and real requests so what’s happening
is this (in case you anyone else has this problem):
Our e2e test runs against our dev env which is pointed at Hubspot Dev
instance, a contact is created as expected for the (ex. “
Our e2e test signs a document via HelloSign, indicating that it’s a test
HelloSign tries to push a reference to the signed document to the Hubspot
contact. However, HelloSign doesn’t have a separate dev instance /
environment feature so it pushes it to the prod Hubspot integration.
Because there’s no matching contact for the signed doc, Hubspot or
HelloSign (dunno which) creates a new contact in the prod Hubspot
environment (“firstname.lastname@example.org”) and pushes the signed document
reference to it
Anyway, not Hubspot’s problem. We’ll take it up again with HelloSign.
Robert_Ainslie https://integrate.hubspot.com/u/robert_ainslie HubSpotter
By that, I mean that it appears your API call is creating the contact in
the dev portal (so, the HubSpot auth is properly directing the creation of
the record) and that the record is then being created by the HelloSign
integration in the non-dev portal. I don’t have insight inbetween those two
steps as to why that’s the case. Does the ‘create contact’ process also
post the record anywhere else?
It seems like they are disassociated processes and not a linear dev-portal