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.

This seems to be an issue that has been addressed over the years, but I haven’t found anything that is current.

I’m trying to create a simple “create customer” zap from Kintone to Quickbooks Advanced. Zapier is not finding our custom field in QBO. 

We only have two custom fields at this time, one is a number and the other is a string (“Text and Number” as selected from within QBO), so we are not exceeding the three custom string-based field maximum enforced by QBO.

We are testing in the Developer/Sandbox area at the moment. I’ve read all the other posts, doc, and blogs referenced here in the forums, but nothing points to a solution. Any help is appreciated.

Hi ​@DANAqs,  welcome to the Zapier Community 👋

 

Thanks for reaching out and providing such detailed information about the issue you’re encountering with custom fields in QuickBooks Online Advanced (QBO) not showing up in Zapier.

 

From Intuit’s documentation, custom fields in QBO will only show in the API response if they meet specific criteria:

1. Field Type and Limitations:

• Only the first three string-based custom fields are included in the API response. Even if you have fewer than three, only string-based fields qualify.

• Since one of your fields is a number, it won’t appear in the API response. This restriction can cause Zapier to miss fields during configuration.

2. Field Availability:

• Custom fields must be enabled for all sales forms (like invoices, estimates, sales receipts) or all purchase forms. If they’re configured for specific forms only, they won’t appear in the API response.

3. Immutable Mapping:

• Even if custom fields are marked as inactive in QBO, their original mapping persists. This can create unexpected behavior if you’ve made changes.

 

I would suggest reviewing the above information and then retesting your trigger. If the issue persists, I would encourage you to reach out to our support team so we can dig deeper:

https://zapier.com/l/support

 

Hope this helps!

I am having the same issue. The custom field was setup as per the instructions above

Reply


Terms & Conditions