Hi everyone! 
I’ve just uploaded my first YouTube video showcasing how to use Flows, and I’m excited to share my experience with you! In the video, I guide you through the basics of setting up a very simple scheduled Flow that automates record deletion. As a long time user of Tasks, being able to automate deletions from within my Knack application is great!
Here’s what you can expect to see:
• An overview of record IDs and why they’re important for integrations.
• Step-by-step instructions for creating a daily Flow to automatically remove records marked for deletion.
• A live demonstration to ensure everything runs smoothly.
As someone new to Flows, I thought this might be helpful for others in the community.
I’d love to hear any feedback you might have!
Visit my channel - over 100 Knack tutorials
2 Likes
Great video! It’s nice to see an example of the iterator step in action! Thanks Carl. 
1 Like
Great video @CarlHolmes and on the notorious Delete feature, automated at that! Between the False Delete and the Flow Delete, all set for safe and clean data base now.
In the video in your Note page, there is a short text field for Record ID. Does that mean that you fill it manually? If so, probably there should be a way to automate it.
But anyway, as you say in the video, it is not needed for the delete Flow cose it already proposes it.
1 Like
He is probably using KTL to fill it automatically - its one of the many great features of KTL …
1 Like
Indeed @LeighBerre96926 - I did use KTL’s _recid keyword to populate them to illustrate the point. 
1 Like
So to delete 1 record, with 3 steps, that would be 3 transactions Flow I believe.
If one wants to Delete 100 records, that would be 300 transactions, 40% of 750 tr. included in the Pro Plan.
In this specific case of False Deleted (Trashed) records, might be better to manually batch delete in the builder once a week/month.
what do you think?
If you have builder access and want to schedule to do it manually. 
1 Like
ohh Indeed, very important the builder access factor. I didn’t consider the user side of it.
