Make Airtable 422 INVALID_VALUE_FOR_COLUMN: match the value to the field type

Fix Airtable 422 INVALID_VALUE_FOR_COLUMN in Make: what each 422 type means, the value each field type takes, Smart links (typecast) and HTTP 422s.

Updated 15 Oct 2026 · ~8 min read

Disclosure: this guide has one affiliate link to Make, marked "affiliate link", and mentions our Fiverr fix service. Error messages, settings and limits come from Make Help Center / app docs, Airtable API docs and Make Community threads 59826, 79365 and 115822 checked on 15 October 2026; anything we could not confirm is flagged for review before publishing. We did not reproduce these in a live Make scenario for this guide. Prices, where mentioned, are as seen from the US.

Short answer: An Airtable 422 in Make means Airtable understood the address but rejected the data. With INVALID_VALUE_FOR_COLUMN the value you mapped does not fit the field type: text into a number field, the text true into a checkbox, a date-time into a date-only field, a name instead of a record ID in a linked field. Open the module's input bundle in History, find the field Airtable names, and convert the value to the format that field type takes.

Everything here works on Make's Free plan. We did not reproduce these errors in our own Make account; they come from Airtable's API docs and threads in Make Community.

What a 422 from Airtable means

Airtable's API errors page lists 422 Invalid Request: "The request data is invalid. This includes most of the base-specific validations." Airtable sends a type and a message with it, and that type tells you which problem you have. Make shows it in the module's error, usually as [422] followed by Airtable's message.

The type INVALID_VALUE_FOR_COLUMN with a message saying a field cannot accept the provided value is the most common one in Make scenarios. Airtable's public docs do not list this type in the errors table, so the exact wording can vary.

422 types and what each one means

Field types and the value Airtable expects

From Airtable's field model reference. Check the field type in Airtable first, then compare it with what Make actually sent in the input bundle.

Fix it step by step

1. Open the failed run in History, click the Airtable module's bubble and read the input bundle. That is what Airtable received, not what the mapping panel shows.
2. Find the field named in the error message. If the message has a field ID (fld…), look it up in Airtable's field settings or the API docs for the base.
3. Check its type in Airtable, then convert in the mapping: parseNumber() for numbers, formatDate() for dates, a boolean for checkboxes, split() for multiple selects.
4. Empty values: if a source field may be empty, map it with ifempty() or leave it out. To clear a field in Update a Record, Make's docs say to use the erase function.
5. Run the module again with Run this module only using the same input.

A rich text field that rejected a long text in Community thread 59826 got the same answer from helpers there: check the field type in Airtable, because the problem is in what the field accepts, not in Make.

Smart links and typecast

Airtable's API has a typecast parameter: Airtable then does best-effort conversion from text and can create a select option that does not exist yet. It is off by default. Airtable's support article says that in Make this option is called Smart links. Make's own Airtable docs describe Smart links on Create a Record and Update a Record as entering names instead of record IDs in linked-record fields, with the linked record created when there's no match.

Typecast is not a fix for every 422. Airtable notes that creating select options with typecast needs creator permissions on the base, and a value that can't be parsed still fails. Fix the value first; use Smart links when you really want new options or names in linked fields.

422 with HTTP or Make an API Call

When you build the JSON yourself, the type is often INVALID_REQUEST_UNKNOWN with "Invalid request: parameter validation failed. Check your request data." In thread 115822 (September 2026) the same webhook request worked with curl but failed from the HTTP module. The replies suggested checking:

• Typographic quotes (“ ”) in a body pasted from a document or chat. The body is then not valid JSON.
• Content type: with Body type Raw, choose JSON in the module, and don't add a second Content-Type header by hand.
• Mapped values: read the runtime input bundle, not the module settings.
• Build the body with JSON › Create JSON instead of a hand-written string.

That thread has no confirmed root cause yet. For general JSON problems see Make Parse JSON errors.

Sources checked (15 October 2026)

• Airtable Web API: Errors, Field model, Create records (typecast)
• Airtable Support: Airtable API: Common troubleshooting
• Make apps: Airtable (Smart links, Use Column ID, erase)
• Make Community: 59826, 79365, 115822

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

What does INVALID_VALUE_FOR_COLUMN mean?

The value Make sent does not fit the Airtable field type, for example text in a number field or the text true in a checkbox. Convert the value to the format the field takes.

Does Smart links fix Airtable 422 errors?

Sometimes. Airtable's support says Smart links is Make's equivalent of typecast, which converts text and can create new select options. Make's docs only describe it for linked records, and unparseable values still fail.

How do I see what Make sent to Airtable?

Open the failed run in History and click the Airtable module's bubble. The input bundle shows the values Airtable received.

Why does the HTTP module get 422 when curl works?

Usually the body differs: curly quotes, a wrong or double Content-Type, or a mapped value that is empty at run time. Build the body with Create JSON and compare the requests.