Image Automation

Is your link turning into an actual file in an attachment field? If you’re visually seeing an attachment in an attachment field, then you don’t need to worry about the link expiring because the link has already turned into an attachment.

Hi Scott,

Thank you for your response. Yes, the link is turning into an attachment and I am glad that my data will not be deleted, however, if I want to continue the automation after the update, the link will not turn into an attachment, correct? Is there a way to use an Airtable Automation to copy an image other than using the link? Or is there a place where I can host the image somewhere else where it will not expire? Would that work?

Thanks!

IF you’re pulling the URL from a formula field, then you will have problems, as discussed in the support article below. But if you just pull the URL from the original attachment field itself, then you will be fine:

Ok, thank you so much! So would I be ok with this:

This is the formula that I am using right now to get the attachment and then I am using an Airtable Automation to paste the result in the attachment field.:
RIGHT(LEFT({Page}, LEN({Page}) - 1), LEN(LEFT({Page}, LEN({Page}) - 1)) - SEARCH(“https://”, {Page}) + 1)

It sounds like you are using a formula field to get the url of an attachment, and then using that url to attach the file to a record in a different table of the same base.

In a few weeks, the url in the formula field will be invalid. You will not be able to use that url to create an attachment in a different table.

Is there a reason why you need to make a new attachment using the url? Could you use a lookup field instead? Could the automation copy the attachment field value directly without going through a url?

@James_Jones No, that will no longer work in November.

Hello,
I looked into this, but I am mainly using the URL, so I have a separate table that just stores the images and nothing else. Then I just have the link copied. Is there another workaround that you know of that would work for this? Thanks!