Hmm, as a data point, I just tested this and it worked fine for me.  Specifically, I sent myself an email with the all of the attachment URLs and they all loaded up fine:

The attachment in question was uploaded in February and here’s the Zap setup:

What are you trying to do with the URL?  What error message are you getting and from where?

Thank you for your response.

The point is, I dont get an error. I just basically upload blog posts that are hosted in Airtable and attach a image, which I upload in my Airtable. The first 2 hours everything is perfectly fine, but after a while the picture disappear and just show a “expired” thumbnail.

Ah, yeah that’s because you can’t use Airtable as an image host; the URLs they provide only work for a short time: https://support.airtable.com/docs/airtable-attachment-url-behavior

You’ll need to either host the images on Ghost or find a general image host for this I’m afraid

​@EK7 

Unfortunately, you cannot use Airtable's attachment fields for permanently hosting images, because the attachment URLs are temporary URLs which will expire after 2 hours of accessing them for the first time.

However, you can temporarily use the attachment URLs when running your automation to download & upload the attachments somewhere else for permanent hosting.

(Or, you can just start off by hosting your images elsewhere, and reference those images in a URL field in Airtable.)

Your 2 options for hosting images are:

1. Hosting the image directly with your blogging platform. (In your case, this is Ghost.)
2. Hosting the image with a cloud storage provider, such as Google Drive.

By the way, if you’re not too heavily invested in Zapier, you may want to consider switching to Make for these reasons:

1. Make’s native support for Ghost is deeper than Zapier. (Same with their support for most apps.)
2. Make is significantly cheaper than Zapier.
3. Make is infinitely more powerful & customizable than Zapier.

If you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is one of the ways that you could instantly trigger a Make automation from Airtable.

Hope this helps!

If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Thanks for your responses, guys. If I use make, is there any function with Make that uploads my files on Ghost by itself? I dont want to manually upload every picture manually by hand in Ghost

Similar to Zapier’s Ghost modules, whenever you are creating or updating a post with Make’s Ghost modules, you are required to use a URL of an image that is already hosted somewhere before creating/updating the post.

If you want to automate the process of uploading the images directly to Ghost before creating/updating the post, you might be able to do that by writing your own custom API calls to Ghost’s API using the “Ghost - Make An API Call” module in Make, but I don’t know enough about Ghost’s API to know if that is possible or not. You may want to ask Ghost if their API supports that.

It might be easier to just automate the process of moving your image from Airtable to Google Drive, and then you can reference the image there.

Check out the Make screenshot below for an example of how you could download a single attachment out of Airtable then upload it to Google Drive… and then create your post on Ghost.

The first module is a webhook, because I like to instantly trigger my Make automations from Airtable (instructions at link). I also give a brief Make tips & tricks video in this thread.

Also, in this Airtable podcast episode, I show how to work with Airtable arrays in Make, which might be helpful for you because Airtable attachment fields are arrays.

Hope this helps!

If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Hm, there’s a bunch of threads about this in the Ghost forums actually, so you may want to have a look there instead!