Set doesn't work if Airtable-field is too long


after passing the n8n-courses I was wondering why I wasn’t able to update airtable in one of my projects although I got no error message.

First, I created a test-field test mT-Nutzer akt. Monat (LÄNDER) copy
Bildschirmfoto 2023-02-14 um 09.04.20
and inserted that name in all nodes.
But then I recognised that somehow the set-node separates the field name :woozy_face: so that I assumed that maybe this could be the reason why no data got updated … :thinking:

So I replaced the name in airtable and all nodes to test Monat and then I saw, that the set-node works as it should and that the automation also was updating my data in airtable. :muscle:

Is there a limit for such names or did I found a bug? :slightly_smiling_face:

Best regards

P.S.: Somehow I appreciated, that the n8n courses are not updated because this made me searching in this forum for solutions. :upside_down_face:

Next scenario same problem …

The reason of separation in the set-node is the “.” in the name of the Airtable-field, right?

So I guess, that I have to rename a lot of airtable-fields … :see_no_evil:

Hi @martin23, have you tried disabling the dot notation in your Set node? This should prevent the fields from being broken down by the node:


This is how it behaves with the default settings:


This is how it works with the option disabled:

1 Like

ahh, nice to know. :upside_down_face:
Thank you.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.