When working with the the Bubble.io-Node the GET request does return text fields, but it does not return references to other data types or geographic locations.
Same problem with the UPDATE request, where it return an error that says the field that I want to update (which is a reference to another data type) does not exist. Here I can update fields that are geographic addresses.
What is the error message (if any)?
None. Only for update request it says that the field does not exist.
Bubble allows you to control which fields are available via the API:
In Settings → API, when enabling the Data API, you must select each data type to expose it. You can choose “View all fields” or select specific fields. If a field (such as a reference or geographic location) is not selected, the GET endpoint will not return it. In conclusion, for your n8n node to receive these fields, they must be actively exposed in the Bubble API configuration.
When updating records, Bubble requires that the record ID be used in the endpoint URL, like this: PATCH https://appname.bubbleapps.io/api/1.1/obj/TypeName/{_id}
In the JSON body, only include the keys you want to update:
{
"field1": "new value",
"field2": 123
}
Bubble does not accept nested objects; only scalar values, such as the ID when updating references.
I was aware of the fact that I need to make fields accessible through the API in the Bubble settings. Everything was set up correctly, but it still didn’t return the fields I mentioned in my post.
I tried it again on Monday, same settings but with a new API key that I generated in my Bubble App for the Data API. Now it works.
Not sure what this caused, but happy it works for me now
