It's been such a crazy week! But with a slither of room to breathe I took time to look at Vesa Nopanen's blog on loop components this morning and decided I wanted to have a bit of a play. You see, Vesa is one of my best mates in IT and we practically talk every day. We organize Teams Nation together. We speak on the circuit together. We have a lot of the same thoughts and interests in the same kind of areas. So this blog really is a follow up to his. I am not going to retrace his steps in this piece, but I am going to start out from where loop components are stored, which is OneDrive. Now, the fact that it is stored in OneDrive makes sense because the loop components in Teams are only available on private chats. This makes me think that when loop components emerge for channels, the .fluid file will be housed in SharePoint. This would be consistent with Teams Meeting Recordings. Yet the fact that they are housed in OneDrive means that we can start using flows and automation with them. That's right. Let's create some flows with loop components, or to coin a portmanteau, let's go 'flooping'. This is a completely experimental blog and there's probably going to be loads of roadblocks. But let's see a few things we can come up with. Just for fun. I'll bet you by the time I have got to the end of this I would have built a flow right to the very end and it didn't work on the very last action.