OpenRuna
Sign in
← Workflows

Microsoft Outlook AI Email Assistant

28 nodes · manual, microsoftOutlook, lmChatOpenAi, outputParserStructured, agent, schedule

Engine
n8n
Nodes
28
Trigger
scheduled/triggered
Source file
1974_Mondaycom_Schedule_Send_Scheduled.json

Workflow flow

IntegrationsManualMicrosoftOutlookLmChatOpenAiOutputParserStructuredAgentScheduleMondayComAirtableMarkdownSplitInBatches@n8n/n8n-nodes-langchain.lmChatOpenAi@n8n/n8n-nodes-langchain.outputParserStructured+4 more
100%
TRIGGER

When clicking ‘Test workflow’

Manual

OpenAI Chat Model

@n8n/n8n-nodes-langchain.lmChatOpenAi

Structured Output Parser

@n8n/n8n-nodes-langchain.outputParserStructured

TRIGGER

Check Mail Schedule Trigger

Schedule

TRIGGER

Update Contacts Schedule Trigger

Schedule

Microsoft Outlook23

MicrosoftOutlook

Monday.com - Get Contacts

MondayCom

Rules

Airtable

Categories

Airtable

Delete Rules

Airtable

Airtable - Contacts

Airtable

Convert to Markdown

Markdown

Email Messages

Set

Merge

Merge

Set Importance

MicrosoftOutlook

AI: Analyse Email

@n8n/n8n-nodes-langchain.agent

Set Category

MicrosoftOutlook

Loop Over Items

SplitInBatches

If

IF

Contact

Airtable

20 steps · flows top to bottom, branches left to right

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Microsoft Outlook AI Email Assistant (28-node n8n automation, manual, microsoftOutlook, lmChatOpenAi, outputParserStructured, agent, schedule, mondayCom, airtable) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

Built in n8n, "Microsoft Outlook AI Email Assistant" chains 28 nodes to move data between manual, microsoftOutlook, lmChatOpenAi, outputParserStructured, agent, schedule, mondayCom, airtable. 28 nodes · manual, microsoftOutlook, lmChatOpenAi, outputParserStructured, agent, schedule It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna shows the full flow diagram, an integration breakdown, and a one-click JSON export for n8n's "Import from file". Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Study how data moves from manual to microsoftOutlook before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the manual stack.
  • Import "Microsoft Outlook AI Email Assistant" into n8n, reconnect credentials for manual, microsoftOutlook, lmChatOpenAi, outputParserStructured, agent, schedule, mondayCom, airtable, and run the same automation in your own workspace.
  • Use it as a starting template when wiring manual, microsoftOutlook, lmChatOpenAi, outputParserStructured, agent, schedule, mondayCom, airtable — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "Microsoft Outlook AI Email Assistant" exposes 28 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, microsoftOutlook, lmChatOpenAi, outputParserStructured, agent, schedule, mondayCom, airtable. Set your credentials on the manual node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "Microsoft Outlook AI Email Assistant" JSON into a plain-English runbook, node by node. It can flag where manual rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for manual, microsoftOutlook, lmChatOpenAi, outputParserStructured, agent, schedule, mondayCom, airtable. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Microsoft Outlook AI Email Assistant" — extract manual IDs and secrets into environment variables without changing the 28-node structure.

Frequently asked questions

How do I import "Microsoft Outlook AI Email Assistant" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Microsoft Outlook AI Email Assistant" use?
It uses: manual, microsoftOutlook, lmChatOpenAi, outputParserStructured, agent, schedule, mondayCom, airtable. The flow diagram above shows how each service connects across the 28 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and microsoftOutlook credentials in n8n after import.
What trigger type does "Microsoft Outlook AI Email Assistant" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Microsoft Outlook AI Email Assistant" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, microsoftOutlook, lmChatOpenAi, outputParserStructured, agent, schedule, mondayCom, airtable.

Related resources