I’m sending data from a Tally form to Airtable using Make’s “Make an API Call” module.
The Problem
The API call fails with this error: [422] Unknown field name: "Project"
The “Project” field definitely exists in my Airtable table, but Make keeps rejecting it.
What I’ve Tried
Rebuilt the scenario from scratch
Recreated the Airtable connection
Checked the field name spelling (it’s “Project”)
Tried the native “Create a Record” module but it won’t detect new fields
Tried using field labels instead of index numbers
My Setup
Tally form → Make Webhook → Airtable API (POST)
Airtable Base ID: appyUArtd9SyBb7kR
Table: Enquiries
Body being sent:
{
"records": [
{
"fields": {
"Name": "{{2.data.fields[0].value}}",
"Phone": "{{2.data.fields[1].value}}",
"Email": "{{2.data.fields[2].value}}",
"Project": "{{2.data.fields[13].value}}",
"Status": "New"
}
}
]
}
Screenshots
[Attach screenshots of the error and my Airtable field names below]
Thanks for any help!
### 🤔 What is the problem & what have you tried?
The "Project" field definitely exists in my Airtable table (I can see it as a column), but Make's API call keeps rejecting it.
What I've tried (nothing has worked):
Checked the field name — It's "Project" in Airtable, and that's exactly what I'm using in the JSON body.
Tried using field labels instead of index numbers — same error.
Deleted and recreated the "Project" field in Airtable (typed manually, no copy/paste) — same error.
Rebuilt the entire scenario from scratch — same error.
Recreated the Airtable connection — same error.
Cleared the webhook queue — same error.
Tried the native "Create a Record" module — but it won't detect the new fields (Phone, Services, Urgency, Project), so I switched to "Make an API Call" as a workaround.
My Setup:
Tally form → Make Webhook → Airtable API (POST)
Airtable Base ID: appyUArtd9SyBb7kR
Table: Enquiries
JSON Body being sent:
### 📋 Error messages or input/output bundles
## Error Message
Here's the exact error I'm getting from the Airtable API call:
```json
{
"error": {
"type": "UNKNOWN_FIELD_NAME",
"message": "Unknown field name: \"Project\""
}
}
### 📸 Screenshots (scenario flow, module settings, errors)
I tested it out using your JSON and everything works.
Please, create a new scenario and add here an Airtable Make an API Call module but without copying it.
Configure it using hardcoded data and trigger the scenario.
If it works we will have two possible causes.
Airtable returns a 422 field name error but it’s not the field name, it’s the content - you will be able to validate it using hardcoded data in your main scenario instead of a mapped value.
Your scenario has some cache problems - it should fetch new Airtable fields using RPC - so having in mind this
it can be a scenario problem. In that case log out, clear browser cache and login once again.
Also, please tell us - have you rebuilt your scenario as a new scenario or by deleting modules and adding them once again or creating a new scenario and pasting the flow?
hank you for your detailed response and for testing my JSON!
Here are my answers to your questions:
1. Have I rebuilt the scenario as a new scenario or by deleting modules?
Yes, I have rebuilt the scenario from scratch multiple times (not just deleting and re-adding modules).
I’ve also tried the native “Create a Record” module, but it doesn’t detect all the fields (Budget, Start Date, How Heard, Services are missing).
2. The root problem I’m facing:
My Tally form has 12 fields. When I submit a test form, the webhook receives the data correctly — I can see all fields in the webhook bundle.
However, when I try to map these fields in the Airtable “Create a Record” module:
Name appears
Phone appears
Email appears
Business Name appears
Services missing
Budget missing
Address appears
Start Date missing
How Heard missing
Status appears
3. What I’ve tried:
Rebuilt the scenario from scratch (multiple times)
Cleared browser cache and logged out/in
Tried both “Make an API Call” and “Create a Record” modules
Recreated the Airtable connection
Added all fields to Airtable table (they exist and are visible)
Submitted fresh test forms with all fields filled in
4. What I’ll try next based on your suggestion:
I will create a brand new scenario and add the Airtable “Make an API Call” module without copying it, and configure it with hardcoded data to test if the fields appear.
Question: When you tested my JSON, did all fields appear correctly in your Airtable? Which method did you use — “Make an API Call” or “Create a Record”?
Yes, created a sandbox database according to your spec and used your JSON as I initially thought that maybe there is some kind of problem with a naming conflict in Airtable.
I used Make an API Call
That’s strange - what else can you do?
Check once again naming in Airtable. Maybe you have Project[space]? Or Project[special character]?
To be 100% sure you can get your database schema using the Get Base Schema endpoint.
What I’m most concerned about - Airtable’s “Create a Record” uses RPC to fetch new fields dynamically each time you open its configuration.
You can force it by clicking the refresh button.
If that’s not working for you- I think you should contact support as we are volunteers here and don’t have access to your account and it’s configuration.
First, that both “Create a Record” won’t detect the new fields and the API rejects “Project” points to a caching or schema-sync issue, Airtable’s API sometimes lags behind UI changes, so try refreshing the schema or waiting a bit. But the more likely culprit: an invisible character or trailing space in the field name, recreating it manually can still introduce that. Also check it’s not a computed/lookup/formula field, those reject writes with exactly this error. Quickest test, hit Airtable’s own API docs page for your base, it shows the exact field names as the API sees them. Does “Project” appear there verbatim? Also worth scrubbing that Base ID from your post.
Solid diagnosis, the API-docs-as-source-of-truth trick is the fastest way to settle it since it shows field names exactly as the API sees them, invisible characters and all. Worth adding: field type mismatches also throw this, e.g. writing a plain string to a linked-record field, which “Project” often is. Linked fields expect an array of record IDs, not a name. And good call on scrubbing the Base ID. Curious what the API docs page shows for that field.
What is your goal?
appears
missing
