Hi there @Karen G,
Welcome to the Community!
Before we dig deeper into this, could you please follow this help article on how to setup Bubble with Zapier:
https://manual.bubble.io/core-resources/bubble-made-plugins/zapier
Please give the help article a read and I'll be keeping an eye out for your response!
Hi Ken,
Thank you - that was quite helpful. I’ve gotten it to connect to Bubble and to pull data from orders when they are placed. However, it won’t pull ALL of the fields from the ORDER table (sorry, “all of the bubble things from the order data type”?). I’ve set up a privacy rule that specifies that the user executing this zap has permissions to view all fields, find them in searches, and allow auto-binding on all of the fields I want to pull in.
However, Zapier just doesn’t seem to see some of the fields. They aren’t shown in the sample data when I test the trigger and they aren’t available in the field list when I try to do the mapping. But I see them under the App data for Orders when I view the records.
Any ideas of where else to look for permissions that might need to be set?
Thanks!
Karen
Hi there @Karen G,
Thanks for the update here.
I did some digging into our notes, and it seems like when you set up your Bubble for access from Zapier, you'll want to follow these instructions that reference enabling the Data API for the data type types you need access to in your Zap(s).
More on how to do that is here.
Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!
Thank you, Ken.
The first thing I’d done during setup of the Bubble connector was to ensure that my ORDER data type was enabled on the API. Likewise, “use field display instead of ID for key names” is also checked. My setup looks like this:
https://share.zight.com/DOuJop0X
It’s my understanding that this then defers to the Privacy setting for the connection to determine which fields are visible. Here’s the privacy setup. The fields that are boxed are the ones that are not coming over to Zapier. It’s not that they are blank - the field itself is not listed as being available in the setup.
https://share.zight.com/rRuB022m
Many thanks!
I appreciate the extra details, @Karen G!
It seems like the next step would be to get in touch with our Support Team on this matter. They'll need to review the logs to verify whether the fields are being captured there. Depending on their findings, they might initiate a feature request or log a bug report, especially if the fields are present in the logs but missing from the trigger's sample data.
You can reach our Support Team here: https://zapier.com/app/get-help
I appreciate your patience and understanding.