How can I find folder paths for a shared mailbox?

[Flashheart]

Hi all. First post and a brand new user to Power Automate - and frustrated already.

I'm trying to test the template which creates a task in Planner when an email comes in to a shared mailbox. Seems simple enough.

I completed all of the requested parameters in the pre-built flow, but it fails and when I run the Flow Checker it tells me the 'folder ID' parameter can't be empty. The template never asked for a folder ID in the first place...

Anyway, I can't find out how to obtain a folder ID for the inbox of a shared mailbox no matter how hard I try! I've searched Google, asked Copilot and searched these forums, but I'm still none the wiser.

Is anyone able to help me out here? These things are NEVER as simple as they pretend to be!

Thanks in advance.

[trice602]

Hi @Flashheart ,

Let's get this resolved this morning.  Can you paste in a copy of your flow screen please?

[Flashheart]

Hi @trice602 ,

Thanks for responding. Is this enough info? Actually, I said 'folder ID' when I really mean 'folder path', as you can see. I still don't know how to find that or format it for the flow...

[trice602]

Hi @Flashheart ,

Please click on edit and then expand your 'when a new email arrives in a shared inbox (v2)' trigger; I need to see the settings.

The issue with templates, in my opinion, is they are not updated frequently and most likely, when this template was created and published, requirements have been added and the template, while still valuable, is not accurate.  I know of a couple of other templates that are no up-to-date.

[Flashheart]

How's this?

[trice602]

Hi @Flashheart ,

Sorry, I know I said setting but meant parameter tabs.

[Flashheart]

Ha. No problem. I should have sent both screens just in case!

[trice602]

Hi @Flashheart ,

Here's the issue.  (Most likely), the template you are using has an outdated trigger.  Delete the trigger and re-add.  Sometimes those definitions will not update in the new designer mode.  Switch to classic.  Delete there, then re-add.  Save.  Retest.

If I switch to code view, I can see my "folderID" is "Inbox" and this works.  I do see you have a folder name selected in your advance settings but not sure if the definition is incorrect or something else.

[trice602 · Accepted solution]

Hi @Flashheart ,

I think I figured it out.  In your advance settings in parameters, for the folder selection, delete Inbox and then use the folder to select inbox, this will provide the folderID.

[Flashheart]

@trice602 Thanks so much. I have a working automation now!

Actually I've learned plenty in the process here - the main thing being not to rely on templates. Now I'm getting the idea a bit more I'll try to start from scratch.

Really appreciate your time and patience on this. Thanks again.

(Have edited the post title to make it more accurate for anyone else finding this problem)

[trice602]

Hi @Flashheart ,

Great to hear!  Glad to help!  I do use templates and refer to them, as framework, and if it works out-of-the-box, great!  I use it but often I rebuild parts of it as needed.

[Flashheart]

Annoyingly, having to revisit this. The task has been working nicely, until an email this morning seems to have thrown up an error. It appears to have an issue with the user who sent the email (they are not a part of our tenant, but then neither are previous senders...).

I'm not aware that the sender is in any way part of the flow, so I'm not sure why this one is occurring. It doesn't appear to be a transient fault as I've tried re-running it and the same thing happened. Wondering what I'm missing. @trice602 if you're around, hate to ask, but your experience would be welcome here!

[trice602 · Accepted solution]

Hi @Flashheart ,

The issue here is that Emma is not part of the tenant and you cannot assign planner tasks to an external user; the sender email is part of the create task flow in your flow; are you assign to the sending and is the root cause.

You could build in a conditional step before the create and check if the sender is from the tenant, such as if sender email is contains '@yourdomain.co.uk' and on the true side, do the true actions (as-is), on the false side, create the task but not assign.

[Flashheart]

Ah. Everything you say makes sense. What's confused me is that none of the other senders have been in our tenant (well, apart from my tests) and the tasks are not being assigned on the way in to Planner - at least they haven't been and I didn't set them up to be. 

I'll have a go at building in your suggested conditional step though, because presumably that will make the flow more robust if that check is properly dealt with.

[Flashheart]

@trice602 You are, of course, correct, there was a field in there assigning a user ID. I'm just not sure why it didn't cause a problem before. I live and learn. It's working now. Thank you again for your expertise.