BundleValidationError w/ Go High Level (Create a Contact Module)

[c_geddz]

Not sure how to resolve this. I have other scenarios that use a search contacts => update contact module flow and haven’t ran into any issues. A previous post was made about this here: BundleValidationError Validation failed for 1 parameter(s) for Go High Level Module

However, it was marked as solved but can’t find any info on this. Any suggestions?

[Probotic_Solutions]

Hi @c_geddz,

The error seems to be related to contact field type and the data being entered for example, entering text into a number field.
To resolve this, you should check the field type and the information being passed.

I hope this helps in resolving the issue.

[c_geddz]

Thanks so much for commenting @Probotic_Solutions. However, I’m not sure what is wrong with the input as I’ve followed a similar structure in other scenarios without issues. I simply am searching for a contact (1st screenshot) followed by an update contact module (2nd) screenshot which is just mapping the contact ID.

[mszymkowiak]

Hello,

• Check the output of the “Search Contacts” module - is it a proper ID? Is your system configured to handle the creation of a new contact if the search does not return any results?
• Check any additional fields in the “Update Contact” module - maybe you accidentally entered a character there?

Your problem is caused by the module trying to pass a value that is not a number in a field with the ID provided in the error.

So it’s either the previous search module returning no results or any other field that should be a number sending a non-number value.

[mszymkowiak]

Thank you for the loom! Your error is really strange as the config looks proper!

What I can suggest - easiest and quickest - try to delete the module–>save the scenario–>refresh the page. Now go to any other scenario where “Update” is working and copy the “Update module” (right click–> copy). Last step: paste it into this scenario, configure mapping and save.

If it succeeds - contact the support team with details for further investigation of versioning problem.

If it doesn’t help - I have two ideas:

1st: You can install Make Dev Tool on your Chrome browser and analyze the request made by the module and the input data.

2nd: Copy the contact ID that caused the error and build a custom API call using the "Make an API call module. For testing without any mapping.
With custom API call there is no input data validation- so as above- if success- contact support as there is something wrong with module. If error will still occur- contact with GHL- probably some contact IDs are not validated properly.