[400] Invalid input JSON on line 1, column 1538: Encountered START_ARRAY token for non-repeated fiel

[FernandoJr]

Hey guys, how is it going?
I'm using integromat to create companies through a workflow. The worflow consists in two modules, Hubspot and Google Sheets. I've a spreadsheet with company information that I'm watching. After this I have a filter that validates if there is a website associate for the company. Then I list all the companies presented in my CRM and put the result in a vector. From this I validate if the name passed in the vector is equal to the name that I watched in google sheets. The final step if the name is differente (there isn't duplicates) is to create a record.

This is the error:

This is the workflow:

This is the filter that blocks duplicity:

Thank you very much for all!

[ranknNice]

Hi guys, I'm also receiving this error on a "Create a Record" (company) module. Even when using the new module. 

[400] Invalid input JSON on line 1, column 484: Encountered START_ARRAY token for non-repeated field com.hubspot.properties.data.PropertyValue.valu

[KBaba]

Hi guys,

I also have same trouble. My Integromat scenarios have not been working anything, since the issue happened. I posted the case to Integromat support.

The operation failed with an error. [400] Invalid input JSON on line 1, column 73: Encountered START_ARRAY token for non-repeated field com.hubspot.properties.data.PropertyValue.value

[dennisedson]

@KBaba , Let us know what you find out with support there!

[KBaba · Accepted solution]

Hi guys,

The issue has finally fixed thanks to intgromat support. My integromat scenario works again.

The solution is to open the hubspot module and close it with the lower button [OK], and then your module has trouble could fix. Reportedly,  there are possibility that some modules settings might be removed, but there is nothing happened to my modules.

I hope you will be successful.

[dvretenar-cro]

Hi,

Integromat made an update on January 14, 2021. Use the new module to create records.

Best regards,

Darian

[FernandoJr]

Thanks man! The support team reached me and explained what was happening and it's caused by a legacy module.

However right now I'm facing a different problem:

And this one:

Both of then appeared when I schedule my scenario to work automatically.

Do you guys have any clue why is this happen?

Thank you!

[dennisedson]

Hey @FernandoJr 

Welcome to the Community!

Going to throw some heavy hitters at this for you

@lynton , @Daniel_Bleich , @jimbanks any thoughts on the error here?