Workaround for expiring attachment URLs

Hello table experts,

The Airtable upgrade to expiring links has broken some of my processes.

I’m storing documents (*.pdf, docx…) in an attachment field, used a formal to extract the download links and Make automation to download those and attach them to emails.

Is there a workaround to make Airtable attachments work or due I need to change to a different system? What comes first to my mind is to roll up records from a separate “attachments”-table with links to external cloud storage.

Thanks for your advice!

Welcome to the community, @Ricardo! :slight_smile:

None of your processes will need to change, but you simply won’t be able to use the formula field for your attachment extraction.

In, just point to the URL from the attachment field itself, download the file from that URL, and then attach that file to your email.

The URL will only be valid for 2 hours, but that won’t make a difference because it will only take a few seconds to download & attach the file. After 2 hours, if you try to grab a URL from that very same attachment field again, it will be a new URL, but that will be totally fine because you’re just downloading & attaching it again.

1 Like

Thanks @ScottWorld, I didn’t realize there was an URL field included and always thought extracting the URL via a formula is mandatory. An easier solution that expected. :sweat_smile:

1 Like

Btw if you are looking for a more scalable solution for storing your assets and getting a non-expiring URLs to use ub your apps, you can use Firebase/Google Cloud storage. and to get a nocode/airtable like experience of using Google Cloud Storage you can use Here is a video on this: Move Airtable Attachments to Google Cloud Storage for non-expiring URLs - YouTube

I am co-founder of Rowy, we made Rowy for solving these kinds of issues when nocode development reaches certain limits of features or scale. Happy to answer any questions if you find this interesting/useful.


Hi Harini, and welcome to the forum.

I haven’t used Rowy much, but I’ve developed an interesting viewpoint about it. I believe Rowy, and other tools like it, define what’s next. And by “next”, I mean when the no/low-code database product segment must undergo a transformation to meet new demands related to artificial general intelligence.

I don’t think the founders and CEOs of the current crop of market-leading no/low-code platforms are ready for what happens after AI reaches the knee of the curve.

We’ve been talking about AI for a few decades now, and quietly, largely undetectable progress has continued. Nothing really big, nothing really impressive. Last year, we hit the"knee" of the curve. (Chain of Thought)

I have a hunch that Rowy is “AGI-ready”. This is to say that it has an underlying design that would support the ability to build applications based purely on instructions abstracted from an AI process. Am I wrong or premature about my hunch?

I recently wrote …

No-code front-ends and back-ends will flourish in the coming years. It will become a race of specialists. No-code solutions will transition into best-of-breed components beginning with the fundamental decision point - Which front-end and back-end do I choose for this project?

I wrote in a little more depth about this here.

BTW, last week I literally wrote a task for myself -

“Try to get in touch with the CEO of Rowy and ask her if she envisions a time when her platform will be able to respond to an AI prompt that describes a database system, and just build it.”


hey Ricardo, can you please detail how you’ve setup this Make automation to download the attachments and attach to emails?

I have a similar table with attachment fields, and when I “send record” directly from Airtable, the image resolution decreases and are pixelated upon zooming. The file names are also randomized. So I am looking for a solution that keeps the original attachment size intact, including the file names preferably

Hi Hafiz, my workflow is:

  1. Iterator loop throughs Airtable attachments.
  2. HTTP module downloads the attachments.
  3. Variable maintains the filename.
  4. Aggregator combines attachments.
  5. Gmail attaches it to email.


Hey Ricardo, thanks for the explanation. I am new to Make and trying to recreate this setup, but running into a few problems. Can you please help clarify:

  1. In my setup, each of the 2 rows of automation is processing only 1 attachment at a time. Is that the way it’s supposed to be?
  2. Every time I run this automation, 2 mails get sent with 1 attachment each. How do I combine into a single mail i.e. I am not able to figure out how the array aggregator works I guess

I can post individual screenshots of the individual module configurations if that helps!