Regression in Airtable node?

Built with n8n
,
1

Hi there

I do update my n8n instance weekly on sunday and yesterday updated to 1.79.3 and some workflow generated errors after this update.

I think there is a bug with airtable node breaking node item matching. Maybe related to this update :

1.79.0 (2025-02-13)

Bug Fixes

  • Airtable Node: Use item at correct index in base/getSchema (#13174) (f2e3586)

Here is an example of simple workflow to show the issue. In the “Edit Fields” node, {{ $('Yesterday').item.json.newDate }} returns undefined while {{ $('Yesterday').first().json.newDate }} work.

In that case I think {{ $('Yesterday').item.json.newDate }} should be valid

2

Am I alone with this ?

3

Sorry to insist but I am a bit surprised that nobody is worried by this artable node issue. Can someone of the team give a feedback ?

4

I’m not sure this is an air table issue. .first() is a perfectly valid syntax and sometimes preferred for pointing to the first item in an execution.

5

Yes but sometimes you don’t want the first item but the matching item. That was working previously and stopped working in recent version @Daniel_Lamphere

6

hmmm maybe try aggregating the results from air table, and then either split out, or loop over the array

7

Thanks but I am not looking for a workaround. I am reporting a regression on something that work before and was broken recently

8

This regression really impacted different production workflows. nobody from the team @Jon ?

9

Hey @Valerian_Lebert,

We did a 1.79.4 release last Friday that should fix, It should also be resolved in 1.80 and 1.81 if you wanted to try one of the more recent releases as well.

1 Like
10

Problem solved