# Airtable input to GPT module - missing field names **URL:** \ **Category:** Questions\ **Tags:** tally, chatgpt, airtable, mapping\ **Created:** [July 31, 2025, 8:53am UTC](https://community.make.com/t/airtable-input-to-gpt-module-missing-field-names/88488 "2025-07-31T08:53:23Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Patrick\_Evans](https://avatars.discourse-cdn.com/v4/letter/p/74df32/32.png) [@Patrick\_Evans](https://community.make.com/u/Patrick_Evans)\ **Post date:** [July 31, 2025, 8:53am UTC](https://community.make.com/t/airtable-input-to-gpt-module-missing-field-names/88488/1 "2025-07-31T08:53:23Z")
Hi everyone, I’ve been going in circles with this and could really use some help. The flow is: **Tally (trigger) → Create record (Airtable) → GPT → JSON → Update record (Airtable)**. Everything after the GPT step works fine, but I’m struggling to pass all the _relevant_ data from the **Create a record** step into GPT. The output from the record creation includes both Airtable column names and answers (e.g. “Brake issue – true”), but the GPT input only shows the answers (e.g. “true”, “false”), with no context. This makes it hard for GPT to return an accurate diagnosis. I’ve mapped all the needed fields manually into the GPT module, and have tried using ChatGPT, aggregators, and set variables—but I still can’t get the input to include both questions and answers together. It’s also worth noting that the Airtable output includes fields I _don’t_ want to send to GPT (like email addresses or internal fields that aren’t relevant to the diagnosis). Any ideas? I’d really appreciate some guidance! ![image](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/2/7/273af54a8ab3f764e22a0d55eefc16e356c4350c.png) ---
**Author:** ![Prem\_Patel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/prem_patel/32/93657_2.png) [@Prem\_Patel](https://community.make.com/u/Prem_Patel)\ **Post date:** [July 31, 2025, 5:50pm UTC](https://community.make.com/t/airtable-input-to-gpt-module-missing-field-names/88488/3 "2025-07-31T17:50:53Z")
Heyy @Patrick_Evans Welcome to the community! Can you please share the screenshots of JSON related Instructions added, expected outputs required to help you on this case? Ideally if you give the Expected response json format, GPT will rercognize it for 1 or more items in JSON array so it’s better to give that json format example in instructions. Like Que as key and answer as value {“Question”:“answer”} or question and answers as keys and respective text as value {“question”:“question text”,“answer”:“answer text”} I hope this helps! Best, @Prem_Patel ---
**Author:** ![Patrick\_Evans](https://avatars.discourse-cdn.com/v4/letter/p/74df32/32.png) [@Patrick\_Evans](https://community.make.com/u/Patrick_Evans)\ **Post date:** [August 1, 2025, 8:45am UTC](https://community.make.com/t/airtable-input-to-gpt-module-missing-field-names/88488/4 "2025-08-01T08:45:12Z")
Hey @Prem_Patel , thank you! The JSON output from the GPT module is working perfectly. I’ve defined the structure in the prompt, and the responses are correctly mapped into Airtable via the JSON and ‘Update a record’ modules. The problem lies earlier in the flow: the ‘Create a record’ module outputs the full question/column titles alongside user responses, but this context is being lost when passed into GPT. Without these labels, GPT lacks the detail needed to generate an accurate response. See the attached screenshot comparing the ‘Create a record’ output with the GPT input and scenario setup for reference. It is essential that GPT input contains the questions/column titles as context to form an accurate response for the user. ![image](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/5/3/538681c4944381cea5e699d88660148e240cf8b6.png) ![image](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/c/8/c85fcf94067f662ae34dc5e59bcf48ccc10cd1a4.png) ![image](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/a/8/a8e275cc621c21c3260e6355931b3320a64c2f06.png) ---
**Author:** ![R-SimplifiedWebhooks](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/r-simplifiedwebhooks/32/3914_2.png) [@R-SimplifiedWebhooks](https://community.make.com/u/R-SimplifiedWebhooks)\ **Post date:** [August 6, 2025, 2:29pm UTC](https://community.make.com/t/airtable-input-to-gpt-module-missing-field-names/88488/5 "2025-08-06T14:29:34Z")
Hi @Patrick_Evans, each module now offers an option to use the complete bundle as a variable (the very first variable of each module). Maybe that helps in your case? 🙂 Alternatively, you could use the HTTP Module to make a request, do not parse the output and insert the output into your AI module 🙂 Best, Richard ---
**Author:** ![Prem\_Patel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/prem_patel/32/93657_2.png) [@Prem\_Patel](https://community.make.com/u/Prem_Patel)\ **Post date:** [August 14, 2025, 3:19am UTC](https://community.make.com/t/airtable-input-to-gpt-module-missing-field-names/88488/6 "2025-08-14T03:19:03Z")
@Patrick_Evans You can map the whole Airtable output Bundle as shown in image below ![Screenshot (981)](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/d/f/dfefb3195dcac35c2d58ab61d5c1916df043eace.png) Best, @Prem_Patel ---
**Author:** ![R-SimplifiedWebhooks](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/r-simplifiedwebhooks/32/3914_2.png) [@R-SimplifiedWebhooks](https://community.make.com/u/R-SimplifiedWebhooks)\ **Post date:** [August 15, 2025, 11:57am UTC](https://community.make.com/t/airtable-input-to-gpt-module-missing-field-names/88488/7 "2025-08-15T11:57:07Z")
Thanks @Prem_Patel for the screenshots, that’s exactly what I was referring to! ❤ ---
**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\ **Post date:** [November 13, 2025, 1:12pm UTC](https://community.make.com/t/airtable-input-to-gpt-module-missing-field-names/88488/8 "2025-11-13T13:12:06Z")
This topic was automatically closed because it's resolved or inactive. Please, start a new topic.