Airtable Module 422 Error

How To
,
1

My scenario was working fine then started getting 422 errors from my first Airtable module, preventing the rest of the scenario from continuing.

RuntimeError
[422] Invalid request: parameter validation failed. Check your request data.

Things I’ve tried without success:

  • adding a new airtable module before it, simpler, with no filtering formula. Same error
  • Checking airtable api status, no issues

I tried airtable api via postman which does work if i configure parameters not in body

Anyone else having issues?

1 Like
3

I had a similar issue last weekend. Switch your base and view map switches to ON and try it again.

2 Likes
4

I got the error to go away but it’s not ideal. Basically there’s a “select all” outputs option in the airtable module. If I select nearly all of my rows except 1 the scenario passes through the module without an issue. But as soon as I select all output fields (manually or with the checkbox) it generates the error. And it’s not because one specific field is throwing the error - i’ve toggled off a few of the fields. Doesn’t matter which one, but as long as 1 field is not selected it works ok. As soon as all fields are selected = error. Gotta imagine this is a make.com issue.

5

Ok another update. I added a few new fields to my airtable table, but when I tried to select them from the airtable module it threw the same error, even if 1 of the fields was left unselected. So the issue seems to be with the number of fields. There must be some maximum number of fields that can be requested from airtable via api or make.com screws up the request to more than 20 or so fields.

6

Can confirm @Alan3 was having the same issue and yes looks like is a max of 20 fields.

Was getting the 422 error when using ‘select all’ (over 20 fields) and then when manually selected a few fields suddenly started working.

Was ripping my hair out trying to figure out what was wrong with my formula, turns out is just limited to how many fields you can output. Not great error messaging…Thanks for your discovery!

2 Likes
7

I’ve spoken with both Airtable and Make support but both say this error shouldn’t be happening. Still don’t have a solution though.

1 Like
8

Can confirm - getting the same issue - maxing out around 20 or so

1 Like
9

Andy - Can you elaborate on this?

I can’t move this table from my base unfortunately

10

I used Postman to identify that the issue IS in fact with make.

As an alternative workaround, I built a workaround scenario

TLDR; Use the airtable API documentation to help me consruct the GET request needed

Then use Make, to use the HTTP module to perform the get request (List records)

Then use the Iterator to make sure my flow is working through all the bundles.

TBH, works very well

11

A small update - Make informed me that this should be fixed. Have not tested though

12

Hello everyone @here

I just wanted to confirm that what @joehanauer mentioned is exactly right.

The issue regarding the Airtable Search records output fields is now resolved and all should be up and running. Ifn case the issue persists on your end, please delete the affected module and recreate a brand-new one from scratch.

Thank you very much for your patience and understanding throughout this process :pray:

1 Like