It would help if there was a node for: Microsoft Outlook Trigger Node
My use case:
Microsoft will soon stop the support of IMAP to get email from Office mail box (cf : “In September 2021, we announced that effective October 1, 2022 , we will begin disabling Basic authentication for Outlook, EWS, RPS, POP, IMAP, and EAS protocols in Exchange Online. SMTP Auth will also be disabled if it is not being used. See full announcement: Basic Authentication and Exchange Online – September 2021 Update.”).
This will prevent EmailReadIMAP node from working with Microsoft Office mail box, and the Outlook node is not a Trigger Node.
Any resources to support this?
Are you willing to work on this?
I’ve got no skills in this domain, so I could not help.
This is a sound request, thanks so much for sharing. Just to make sure you’re aware, you can already implement a “pseudo-trigger” if you like by combining an Interval node with the regular Outlook node (which is able to fetch emails from Exchange online/MS365). An example workflow (fetching unread messages and then marking them as read) would be here: IMAP Email - Error: LOGIN failed - #2 by MutedJam
I am in the same case as you. It would be interesting to have a Microsoft Outlook/Exchange trigger to interact with a mailbox in order to be able to use the workflows after the IMAP block by Microsoft.
I know this is an old thread. I found myself wanting to use my on prem exchange servers to send mail as well as manage the calendars and have access to the GAL and user contact lists. The only way that I found to achieve this was to write an EWS proxy that received payloads from the workflows based on the action requested. The EWS proxy hits EWS with a service account that has impersonation ability. The request user identity is sent along in the json payload to the proxy. So if jschmoe asks the agent to do some rag, summarize the results and email them to danda’man as well as set up a meeting tomorrow at 5 to discuss the results, the agent would make calls to a search-gal tool to look up Dan’s address, and then to create-email tool to send the email with the result summary, and the finally it hits the availability tool to check the recipients availability and if clear it hits the create-meeting tool to set up the meeting. . There are tools to change or delete the meetings, and also search the impersonated users contacts. It’s a pretty helpful proxy for these actions against EWS especially since N8N cannot authenticate directly to it. I run the proxy under a small docker container and use ngrok to expose the webhooks to the tool calls so I can hit it from my cloud instance. I’ll post It to GitHub if there is any interest.