Outlook Trigger shared mailbox "AllItems not found" — production solution on 2,500 execution/month plan?

Questions
1

Running n8n Cloud on the Starter plan (2,500 executions/month). Need to monitor a Microsoft 365 shared mailbox (info@company.com) and process incoming emails through a classification workflow.
What we’ve tried:
Microsoft Outlook Trigger with “Use Shared Mailbox” ON and UPN set to info@company.com. The authenticated account (nicole@company.com) has Full Access to the shared mailbox. Error:

“The specified object was not found in the store., Default folder AllItems not found.”
Why the obvious workarounds don’t work:

  • Schedule Trigger + Graph API polling — 1,440+ executions/day blows the 2,500/month limit
  • Power Automate HTTP connector — requires Premium license, not included in their M365 plan
  • Forwarding info@ to nicole@ — floods primary inbox, not acceptable
  • Re-authenticating credential as info@ directly — shared mailbox has no direct login
    Current plan: Azure Logic Apps (~$0.05/month) to watch the shared mailbox and POST to an n8n webhook. Already built the n8n webhook side.
    Question: Is there a simpler native n8n solution we’re missing? Has anyone solved shared mailbox monitoring cleanly within a low execution budget?
3

Honestly, I don’t think this is really a Full Access problem — it’s more of an Outlook Trigger / Graph folder thing. The error is pointing at AllItems, and shared mailboxes can get weird when the tool tries to bind through that default folder.

The easiest fix on a tight budget is probably what you were already thinking: have Azure Logic Apps watch the mailbox and POST to an n8n webhook. That way n8n is event-driven and you’re not wasting executions on polling.

The one native n8n thing worth trying first is just hardcoding the shared mailbox as info@company.com instead of letting it try to pick or look up the folder. But if it’s still going after AllItems, I’d stop banging your head against it.

Honestly, Logic Apps → n8n webhook isn’t really a workaround here — it’s probably just the better setup for a low execution plan anyway.

4

good day @Brian_Magladry
I’d check one thing before closing this as a workaround case. In the Microsoft Outlook Trigger, confirm whether the shared mailbox option lets you target a concrete mail folder like Inbox instead of a virtual folder like AllItems, because the error suggests the node is trying to resolve a folder that does not exist in that mailbox context.