Suppress Duplicate Record "Error"

Developer Support APIs & Integrations
1

We are using a jetpack custom form to send information to HubSpot (just anticipating why using jetpack it is to work around issues that we have encountered with HubSpot forms which is another discussion). The issue is we are getting a “status”:“error”,“message”:“Contact already exists. Existing ID:XXXXX” returned to us. Because this is coming back with the status “error” we are not proceeding to form complete. Note we anticipate we will get duplicate requests, and we will process then, this should not be an “error”, but a warning.
Can this “error” message be turned off?

2

Hi, @NCosgrove :waving_hand: Thanks for your question.

To help you better, can you provide additional information about your setup, such as:

  • How are you currently handling the form submission and API calls to HubSpot?
  • Are you using any specific Jetpack settings or custom code that might affect the response handling?
  • Can you share any relevant code snippets or error logs?

With more details, the community might be able to provide better suggestions for addressing the issue. It might also be worthwhile to reach out to Jetpack support, as they could have more insights into the specific behaviour you’re encountering with their forms.

Best,

Jaycee

3
  • We are handeling the form submission per the HubSpot instructions using OAUTH. Note as described there is no problem in the form submission, we are getting results and triggering workflow in HubSpot
  • The issue is that Hubspot is return a response code of Error as Hubspot is detecting that there is already a record with that email, but in our scenario a duplicate is not an Error.
  • Because the JetForm sees an Error retuned in the Hubspot response code it is showing the error on screen and is not displaying the confirmation message even though Hubspot took the submission.
  • We have of course reached out to JetPack, but given they are correctly processing the incorrect error warning that HubSpot is sending it is hard to see what they can do

Respectfully, if HubSpot accepts the form submission and kicks off workflow processing then it should not be returning error.