Problem with image urls and parameter validation

Questions
1

I’m building a scenario in Make.com that takes image URLs generated by ChatGPT and posts them to social media (Facebook/Instagram). The scenario keeps failing with errors like:

  • “Only photo or video can be accepted as media type (9004, OAuthException)”

  • “Validation failed for 1–2 parameter(s)”

  • “Record with key … does not exist”

The URLs coming from ChatGPT look like this: https://oaidalleapiprodscus.blob.core.windows.net/...

These links expire quickly, so by the time Make tries to fetch them, they’re invalid.

What I’ve Tried

  • Passing the URL directly into the Facebook/Instagram module → fails because the link is expired or not a valid file.

  • Re‑running the scenario → same error.

  • Checked parameters → some required fields are filled, but the media field doesn’t accept the URL.

I want to know the correct way to handle expiring URLs from ChatGPT so that I can:

  1. Download the file immediately when the URL is generated.

  2. Store it somewhere permanent (Google Drive, Dropbox, Make Data Store, etc.).

  3. Pass the binary file into the social media posting module.

I’m not sure how to set up the HTTP module and connect it properly, or how to store the file for later use.

How should I structure my Make scenario (modules + connections) so that:

  • ChatGPT’s expiring URL is downloaded right away,

  • The file is saved in a permanent location,

  • And the social media module receives the actual file instead of a dead link?

3

Welcome to the Make community!

After downloading the file,

You’ll have to upload the image to a service that can provide you with a direct link to the image.

Examples of such services include Imgur, Flickr, and Cloudinary.

You can also use Amazon S3, Google Cloud Storage, etc. You can find more file hosting integrations here: https://www.make.com/en/integrations/category/storage.

1028×464 64.9 KB

Hope this helps! If you are still having trouble, please provide more details.

— @samliew