Gsheet>notiondb error [400] mismatched data type: title/rich_text

How To
, , ,
1

What are you trying to achieve?

my objective is to send contact info from gsheet (watch new rows) to a notiondb (create new db item). configuration: the column headers in gsheet match the property names in notion. the notion properties are all text type formats. connection is working. permissions are fine.

when I use the “choose from a list” option, then just match each field with the corresponding field, it throws “error [400] type mismatch between request for property ‘title’. got type ‘title’ and expected type ‘rich_text’ from database schema.”

Steps taken so far

[1] in the gsheet module, I’ve tried each of the advanced configs: formatted-mapped, formatted-unmapped, unformatted-mapped, unformatted-unmapped.
[2] reformatted gsheet values to plain text, then back to auto.
[3] attempted to manually map in to control the data type (which I changed to rich text, per the error message); oddly it returned the same code but said it wanted type title rather than rich text. when I swapped it to title type, it asked for rich text. oof.
[4] reset the connection itself (meaning delete and reconnect), used a different test db, and reset the modules by deleting and starting over.
[5] I even went back to school for this! that is I reviewed some of the make academy lessons to see if there were any relevant nuggets.

[*] I considered creating a data store module to force reformat, but thought that might erode the value prop because, ya know, that introduces a 3rd db to deal with. I don’t think make.com intended custom data stores/structures to be used for simple flows like this.

I found another post that seemed to discuss a very similar problem, but the make.com mod said that issue was “fixed.” nevertheless, the recommended workaround for that issue was to manually map. I couldn’t find any tutorials or how-tos specifically for manual mapping, so maybe I did action [2] incorrectly.

I’ve spent way way too much time troubleshooting this; what say you, make community? what dumb or obvious thing am I missing?

Screenshots: scenario setup, module configuration, errors

oiuzxdl.png
oiuzxdl.png862×1638 111 KB

weqrqwe.jpg
weqrqwe.jpg2772×1891 222 KB

2

Hi Mike,
You could try changing the property name “title” in Notion to something different. I suspect a possible reason for this error is that “title” is a property type in Notion and the API and there could be a conflict because of this

2 Likes
3

thanks! I did two things based on your recommendation: I changed the notion title-type property to ‘title’ and changed the existing text-type property entitled ‘title’ to ‘role,’ and as a result the default mapping worked perfectly.

I so appreciate your help. I’d like to understand the problem a bit better. this is all new to me, and up until now my assumption has been that labels (like a property name) are functionally inert, for lack of a better term. they aren’t manipulating the data in the same way as functions.

but this experience seems to indicate that the label was playing a more dynamic role. is that an error in the api, or have I stumbled onto a new topic to dive into?

4

nice! It looks like this is an API/Make-specific error, because in the Notion API, “title” is a property type, and for some reason if you create a property named “title” (i.e., same name as the property type), the API throws a conflict error

1 Like