Improving the Files Field: Naming, Sharing, and Organization

Ideas & Features
21

agree :100: with this

1 Like
22

if you don’t mind, can you share the details of how you called the entity description and file from the API inside make?

23

Hello @Edan ,

We have added url and urlExpiresAt to File entity in GraphQL. So If it suitable for your need, you can pull Entity with fields, rich text fields and file urls in one go.

You can explore our graphql editor here.

In my case the query look like this:

{
  findDbFilesNews{
    id,
    name,
    description {md},
    cover {
  		secret,
  		url,
  		urlExpiresAt
    }
  }
}

Screenshot 2026-01-14 at 19.01.07
Screenshot 2026-01-14 at 19.01.07870×1081 72.7 KB

Screenshot 2026-01-14 at 19.01.00
Screenshot 2026-01-14 at 19.01.00863×1136 109 KB

1 Like
24

Thanks for adding those fields to GraphQL!

Any chance url and urlExpiresAt could be added to the regular query API schema (the one used in automations)?

Right now I’m able to get the file secret through an automation query, but I still need to make an extra HTTP call in Make to extract the CloudFront URL from the redirect.

If those fields were available in automation queries, I could handle all the data prep in Fibery and keep Make focused on just posting to social platforms.

Would simplify the workflow a lot.

25

If you’re talking about query to ‘api/commands’ than there almost no chance it appears there. On the other hand if you’re using Automation Script Steps, AFAIK you can use there GraphQL query, see here.

Can you share your setup somehow? The words doesn’t do a good job here.