Deep links - the mystery remains... :)

Hi all,
Some background:
Glide’s new feature announcement

Going back to David’s announcement here

And discussed in detail here

Well, I’m trying to make sense of it all.
How can we approach the need to allow deep links, for example to the client details/row?
Knowing that the links are dynamic (“changing”), has anyone been able to build a Make scenario (or App Script) that updates a short URL with the up-to-date links?
The endgame is to have something like this: “”. Or similar for other parts of the app, such as resources, events, etc.


The links were only dynamic if you made major structural changes to your app, such as moving tabs around. Otherwise they were pretty stable.

Glide has recently changed the structure of urls so they are much shorter, and they are no longer base64 encoded. Basically it has a short code to indicate the tab you are on, a code for the screen, as well as the row ID. So urls are much more predictable than they use to be, but I’m not sure if they still exhibit any vulnerability as far as changing when the structure of the app changes. I haven’t tested that yet.

But now they are structured something like this for a tab level screen:

And something like this for a detail screen for a specific row item that’s embedded within a couple of screens:

I think the code after the dl/ is the tab code. Each code after s/ is the code for that screen. And the code after r/ is the row ID of the final details screen.

I don’t know how vulnerable those tab codes and screen codes are, but if they are stable and unchanging after moving tabs and screens around, then it should be pretty easy to use a template column to retrieve the deep link in a column and not worry about them changing.


I have an example that uses to generate branded shortlists of glide deeplinks.

Is this something you’re looking for?


Great to hear from you and a great app, as always.
Can you please direct me to where the shortened link comes into play? I couldn’t find it.

When they share their profile, it’s a branded shortened link.



Basically the setup should be:

  • When a new row is added, you send the deep link of that row to, alongside your intended “slug”

  • generates the link

  • You update the link back to a column in your database.

  • Point the share button to share the link

I have founded that you can update the link’s metadata, @Robert_Petitto , so it would be nice to have that as an option in the app (say you can give your users the ability to edit the title, description or image).

But that’s only when they share that specific link, say it won’t work when they copy the URL from the address bar of the browser. At the moment, does allow you to “mask” a link (say when you open the share link then the share link stays on the address bar, instead of the original link). However, that does need to have authorization from the original link’s owner, in this case Glide. Would be a nice thing to have to fully “own” our URL.


That’s great, thanks.
What I needed to know (and have already been answered) is that the deeplink won’t be changed by Glide.

Normally, no, but it was recently changed when apps switched over to the new computation model so that it falls in line with how Glide Pages works.

1 Like

Hey @ThinhDinh , thanks for being ever so helpful!
Would you mind elaborate a bit on how to send deep links to with slug? Is it to use services like Make?

Yeah, I almost always use Make to do something like that.

Basically you send the original Glide URL plus the slug you want (usually it’s a “kebab case” formatted version of the row’s “Title” value) through webhook to Make.

Then I process that with a module in Make, and use the Glide API to update the resulting link back to my database.