Hi Scott,
I looked at this and even thought about keying it in quick like. But the more I think about it, the issue is the folder doesn't exist and there isn't a connector (a direct connector) to create a mail folder. I think you can probably do something with Graph but don't have an example readily available. BTW: I did lookup this up in ChatGPT and it is pretty easy to do with the right permissions.
But the root cause here is the folder Scott doesn't exist. You can test this and verify my findings by manually creating the folder Scott, then resubmitting your flow. The other issue why I would revisit if this was my project, is putting emails in first name folders may not be the most effective; meaning you could get a handful of different Scott emails from different "Scott's" which will devalue the folder segregation in my opinion.
One thing I have done in Shared Mailboxes is to simply create a rule and move emails into folders based on the sender's domain name, such as 'microsoft.com'
All that said, even if I needed the original concept of creating by first name only, I don't know that I would use Power Automate because email rules are move effective and you would need to setup it up one time and then click 'run rule now' then it is permanently running.
So consider adding Microsoft Graph API http request to create your folder above the move email step, if needed. Hope this helps.
------------------------------------------------
⭐ If this was helpful, please like and mark as a verified answer to help others find this too!
Always glad to help! 💯💯💯💯💯
Tom
Follow me on LinkedIn - Thomas Rice, PMP | LinkedIn