Glide API Delete Rows

I’m currently on the starter plan of glide so can’t check this out for myself just yet. Will be upgrading upon go-live.

I need to delete rows of data after 30 days. Ideally I’d use the API to get row that are 30 days old, export them to csv and then delete the rows using Make, however, I don’t see a way to get rows in the API docs, so is this even possible?

If not, the alternative is to do it via Airtable I guess.

A Get is only available on Business and Enterprise plans.

Argh :frowning: don’t have anywhere near the budget for that

Are you able to just do the following:

Use an ITE on the table you want to delete rows on and state IF Date Created is > 30 days old, “DELETE”.

Then on your user table, create a Single Value that just says “DELETE”. Next, create a relation between both DELETE. Finally, create a button that only you can see that has an action of Delete Row attached to the DELETE relation. This will delete all rows that are 30 days old.

Its manual vs automated but only gotta do it once per month

Needs to be automated, it’s for a client so can’t have manual dependencies that rely me unfortunately.

You could attach @Joe_Gabriele method to any inline list or button in your app. Your client will perform the action unknowingly.

Essentially while the customer is using the app he is deleting old rows for you.

FYI Glide just rolled out delete rows through multiple relations. (Delete many rows at once)

Yes Jeff mentioned this, could be the way forward, need to explore it however I need to export the data before it is deleted so not quite as straight forward as that

1 Like

You could export the data in the same action.

Potentially you could hide the rows instead of deleting them by flagging an additional column with “hide” or anything really that satisfies an ITE column.

I.e. If col A is “hide” then blank… else Name

If you are using row owners you could just remove the row owner via Set Columns but I don’t believe set columns works with multiple relations… yet

1 Like

Yes I’d planned to use this to export to CSV too, the problem is control.

Unfortunately it is not quite this straight forward a this, if I build in the delete rows that are 30 days old by relation and export to CSV from one button, then it would work for deletion, but the export would be overkill, and way too many emails would be generated. I don’t need 10k CSV exports a month :wink:.

I need to give it some deep thought as im sure there is a way to get it to work but without being able to schedule an automation it does become a real pain.

Hence I’m thinking airtable might be the way forward for this part of the app. It will allow delete on schedule and on demand export via webhook and Make, or even on schedule export.

I just need to consider what affect this will have when it comes it update usage.

All becomes rather complex with so many factors and limitations at play!

What I would do is add a “last deleted/ modified” time stamp to the action. Then have your action check if that timestamp is within the last 30 days.

I.e. if last modified timestamp is within 30 days then do nothing… else export csv, delete old rows, and update last modified.

I’m not familiar with AirTable so I can’t give any advice on that end.


Oh I didn’t think of that! That might very well work! Thanks, got a few ideas to work with :slightly_smiling_face:.

I shall report back :slightly_smiling_face: