Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Zapier Tables trigger showing internal field IDs (F3, F8) and "New/Old Data" instead of column names

  • February 4, 2026
  • 5 replies
  • 34 views
I
Forum|alt.badge.img

Hi everyone,

I’m struggling with a mapping issue using Zapier Tables as a trigger (New or Updated Record).

Even after creating clean test records and naming all my columns correctly in the Table, the Zap editor keeps showing internal field IDs like "Old Data F 3 Label" or "New Data F3" instead of the actual column labels I've set (e.g., "Volunteer Name" or "Task Status").

 

Here is what’s happening:

  1. I see a mix of "New Data [Internal ID]" and "Old Data [Internal ID]" fields even when I'm testing a brand new record.

  2. My actual column names do appear but often show "(no data)", while the corresponding "F" field contains the actual value I need.

  3. If I map the "F" fields, I’m worried the Zap will break if I ever change the table schema or add new columns.

What I’ve already tried:

  • Deleting all records and creating a new "perfect" test record.

  • Clicking "Refresh Fields" in the Action step.

  • Using "Find New Records" in the Trigger step multiple times.

Is this a known caching issue with Zapier Tables, or is there a way to force the editor to only show the "Label" names and hide these internal system fields? It makes mapping very confusing and feels unstable for long-term use.

Any help or workarounds would be greatly appreciated!

Best answer by Ivana

Just wanted to double-check whether you’re also seeing the the column names appearing correctly now, or if you managed to sort it a different way?

Hi Sam, I still see the column names with New/Old, Label 5/8 instead of correct column names, but now I understand how that happened so I am fine with that. ChatGPT expained it happens when I have Linked Records in the tables. Let me copy/paste the explanation: 

‘A Linked Record does not store text. It stores the ID of another record. The human-readable value (for example a person’s name) is only a label attached to that ID.

When the trigger is an Updated Record, Zapier generates internal diff fields to represent what changed during the update. For Linked Record fields, Zapier exposes these as:

  • New Data F x Source → the linked record ID

  • New Data F x Label → the display value (label) of that linked record

These New Data F x fields are not real columns from the table. They are Zapier-generated fields created only for that specific update event, based on the sample record Zapier captured.

This is why:

  • The original column name may not appear with a value

  • The (New) / New Data F x fields show data instead

  • Manually entering text into that field later causes an error (because Zapier expects a record ID, not text)

The behavior depends on the sample record used by Zapier and whether the linked field had a value at the moment of the update.’

5 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • February 4, 2026

Hi ​@Ivana 

Try opening a ticket with Zapier Support to report the issue: https://zapier.com/app/get-help

⚡ Troy Tessalone - AutomationAce.com | Top Zapier Solution Partner | #1 Zapier Community Contributor
    I
    Forum|alt.badge.img
    • IvanaBeginner
    • Author
    • Beginner
    • February 4, 2026

    Thank you for reply!

    I already asked ChatGPT and Gemini for advice, think I managed to sort it out :) 

    SamB
    Community Manager
    Forum|alt.badge.img+11
    • SamBCommunity Manager
    • Community Manager
    • February 9, 2026

    Glad you got it sorted ​@Ivana! 🙌 I had a look in one of my own Zaps that is using Zapier Tables, and it only had the column names appearing instead of a field name like “New Data [Internal ID]”. So it seems our engineers may have recently pushed an update to get the column names to appear instead of the column field’s ID reference.

    Just wanted to double-check whether you’re also seeing the the column names appearing correctly now, or if you managed to sort it a different way?

    Looking forward to hearing from you! 🙂

    I
    Forum|alt.badge.img
    • IvanaBeginner
    • Author
    • Beginner
    • Answer
    • February 9, 2026

    Just wanted to double-check whether you’re also seeing the the column names appearing correctly now, or if you managed to sort it a different way?

    Hi Sam, I still see the column names with New/Old, Label 5/8 instead of correct column names, but now I understand how that happened so I am fine with that. ChatGPT expained it happens when I have Linked Records in the tables. Let me copy/paste the explanation: 

    ‘A Linked Record does not store text. It stores the ID of another record. The human-readable value (for example a person’s name) is only a label attached to that ID.

    When the trigger is an Updated Record, Zapier generates internal diff fields to represent what changed during the update. For Linked Record fields, Zapier exposes these as:

    • New Data F x Source → the linked record ID

    • New Data F x Label → the display value (label) of that linked record

    These New Data F x fields are not real columns from the table. They are Zapier-generated fields created only for that specific update event, based on the sample record Zapier captured.

    This is why:

    • The original column name may not appear with a value

    • The (New) / New Data F x fields show data instead

    • Manually entering text into that field later causes an error (because Zapier expects a record ID, not text)

    The behavior depends on the sample record used by Zapier and whether the linked field had a value at the moment of the update.’

    SamB
    Community Manager
    Forum|alt.badge.img+11
    • SamBCommunity Manager
    • Community Manager
    • February 10, 2026

    Thanks so much for sharing this info ​@Ivana! You’re right, I checked on a different table that used linked records just now, and I saw similar references appearing for the field names. 

    Seems like you’re all set for the moment, but please do reach back out if there’s anything else you like some help with. In the meantime, happy Zapping! 😁⚡

      Terms & ConditionsAccessibility statement