Wrong Attachment Filename Display from Airtable

Bugs
1

We’re experiencing a problem with some of our Airtable attachments:

Certain PDF files, uploaded automatically via n8n and Google Drive, are displayed in Noloco with the filename “UC”, even though the correct filename is shown in the Airtable frontend.
When uploading “test.pdf” manually, the filename appears correctly in Noloco, but with many other auto-uploaded PDFs, Noloco shows the filename as “UC” or a similar placeholder.

We have checked:

  • The filename is always displayed correctly to us in Airtable.

  • However, the Airtable API returns an attachment object where the filename property is “UC” instead of the visible filename.

Could Noloco use the same filename as shown in the Airtable UI for users, or provide a way to access/display that “visible” filename instead of the raw API value?
Alternatively, is there a recommended solution or workaround for this issue within Noloco?

dragon_4eiZv34oJX-clean
dragon_4eiZv34oJX-clean211×205 3.44 KB

That’s what I see

2

Hi @JHMS - we take the filename from their API, we don’t have access to anything else (they might be getting it from the URL).

However, I think the simple solution here is for you to provide Airtable with the filename when you’re uploading the file.

They have a filename parameter, which, when filled will be used as the filename.

More here: Airtable Web API

In our experience, leaving this empty leads to unusual situations like this

3

Hi @darragh ,
Thank you for looking into the case.

I will briefly explain in detail what happens.
Step by step:

  1. The files are placed in Airtable in a table by n8n. NoLoco displays them correctly.
  2. An Airtable automation (Create Record) copies them to another table. NoLoco only displays the files with UC.

I have no way of influencing what is written in Airtable.

In Airtable, the file is displayed with the correct file name in both tables.

When I export a CSV from the second Airtable table, the file name and URL are displayed there.

Could it be a caching problem?

Or is noloco reading the files at an inconvenient moment?

Is there any way I can force it to re-read them? Unfortunately, resynchronizing the database doesn’t help.

The Airtable Team Wrote:

We recommend reaching out to Noloco’s support team to investigate whether:

  • They’re modifying the filenames after retrieving the attachments from Airtable,

  • There’s any transformation or file-handling logic applied during sync,

  • Or if there’s a setting that controls how filenames are preserved when displaying or storing external files.

Can I provide any tests or data to narrow down the problem?

4

We simply take the filenames as they are provided by Airtable - if they’re changing them after they’re created, we possibly don’t handle that.

If you can create something we can simply recreate, we would take a look, but it doesn’t really sound like an issue on our side if I’m honest, otherwise all filenames would be incorrect.