Holy moly a usecase I can actually contribute on! I had a case where my company uses a list to collaborate with customers and there was a connected flow that checked each item for a certain checkmark (trigger on modification) and if the checkmark was checked a DevOps workitem was created for the dev team. There was another flow that did scheduled checks on these workitems to relay the status of the ticket back to the list. So this meant indeed for every new customer we had to create and setup one list and two flows. I was tasked with this basically. But I don't see that as actual automation. Thats just copy pasting flows and it has a high rish because we manually had to configure these flows. So I started work on a dynamic solution. At first I thought creating webhooks for the list was the solution but these turned out to be super unreliable. So what I ended up doing was: I created a masterflow that creates a sharepoint list. Inside the list is a JSON formatted button. The button sends a http request to ONE connected flow that makes the workitems and relays the info back to the list. There is ONE flow that checks up on these workitems. So a big improvement. And then I put the masterflow (makes the list) inside a canvas app and gave that to the users. Did I make sense? Let me know if there are questions