I’m running n8n self-hosted on a local server, using a local IP address that is not exposed to the public internet.
Everything works except Outlook Trigger (On New Email – Microsoft Outlook node, OAuth Azure app).
The trigger fires only when I manually activate the workflow.
After that, no new executions happen, even though new emails arrive.
Is this related to:
my hostname not being exposed publicly?
Microsoft Graph needing a reachable webhook callback URL?
or something else in Outlook/Azure config?
I want to confirm if Outlook triggers require a publicly accessible URL, or if they can work on a private/local IP.
No error message.
The trigger simply does not run unless I manually activate the workflow.
If you’re running n8n locally and encounter issues with the Outlook trigger, you may need to configure the WEBHOOK_URL environment variable to point to a publicly accessible URL (using services like ngrok), similar to other webhook-based triggers.
So yes, is needed.
Toggle the button to active , and it will listen in background for events(you can check execution tab for history).
Thank you @Parintele_Damaskin for the clarification !
Just to confirm: I will expose my local n8n using ngrok and set WEBHOOK_URL to the ngrok URL.
I do NOT need to change my existing OAuth Redirect URI in Azure, correct?
Since OAuth and webhook callbacks are separate, and OAuth is only used for the initial connection.
The WEBHOOK_URL environment variable is used for webhook-based triggers (like Telegram, Discord, etc.) that need to receive incoming HTTP requests from external services.
However, OAuth authentication uses a different redirect URL that n8n generates based on your configuration, when you set up OAuth credentials (like for Google, Azure, etc.), n8n displays an “OAuth Redirect URL” that you must register with the OAuth provider.
