Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hey folks,

   I wanted to know if anyone has faced this error and was able to troubleshoot it properly between Niceboard and Google Sheets. I want a new job to be created each time a new row in Google Sheets is filled.

Hi @parker 

Good question.

We would need to see screenshots with how your Zap step 2 is configured.

Is there anything in particular I should share? Here is a general overview of my Zap

 

@parker 

Depends on the Zap trigger step example record data you are testing with, but the 2 Company fields and the 2 Location fields have conditional requirements.

Company ID and Location ID are dropdown fields which expect certain internal values if being passed dynamically.

 

Hi @Troy Tessalone I’m experiencing the same issue. I’ve tried leaving the company and location ID blank, filling them in, and other combinations but still get the same invalid payload message.

I have the same pics essentially as @parker. Any advice on what to do?

Hi @BT1000 

You may want to try reaching out to Niceboard Support for guidance about their Zap app integration.

Did you figure out a way to avoid this error? What was wrong.

Reply


Terms & Conditions