Outlook
Configured with Agent, OpenAI Chat Model, Microsoft Outlook Tool, Microsoft Outlook Trigger. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- AI & models
- Messaging
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Connect Outlook & Set Filter | Trigger | Microsoft Outlook Trigger | See node parameters |
| Add OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Add AI Agent Instructions | AI & models | Agent | See node parameters |
| Reply to Email | Messaging | Microsoft Outlook Tool | reply |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
microsoftOutlookOAuth2ApiopenAiApi
Workflow notes
Sticky Note
Trigger Action
- Connect a Microsoft email account you can authenticate
- Trigger is set to "message received" and the output "raw"
- Add the email address(es) you want the AI agent to handle
Sticky Note1
Agent Instructions
#role You are an AI assistant specializing in replying to incoming emails to [YOUR NAME] Outlook inbox.
#capabilities and limitations Your reply will be limited to the current email message, not the email string. Do not hallucinate.
#response Reply in a casual, modern, professional, concise writing style. You should sound like [YOUR NAME HERE]. Here are examples of [YOUR NAME HERE] voice: [COPY & PASTE REPLY SAMPLES FROM YOUR EMAIL] [COPY & PASTE REPLY SAMPLES FROM YOUR EMAIL] [ADD A VARIETY OF REPLY SAMPLES SO THE AGENT UNDERSTANDS YOUR TONE & STYLE]
Sticky Note2
Add AI Model
- OpenAI Account Credentials Required
- Select model (ie. gpt-4o-mini)
Sticky Note3
Reply Settings
- Manually set the resource, operation, and message
- Toggle switch to reply only to sender
- Let the AI model define the "message"
- Additional fields for the "reply to" and "subject"
Sticky Note4
Draft a Reply
- Follows all the same "Reply to Email" settings EXCEPT the email reply is saved in your DRAFTS folder
- This setting is great if you want a human checkpoint before sending
Outlook
Outlook
Purpose and structure
This folder contains the Outlook workflow. Its executable nodes use agent, lmChatOpenAi, microsoftOutlookTool, microsoftOutlookTrigger. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Connect Outlook & Set Filter
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Microsoftoutlook/1925_Microsoftoutlook_Microsoftoutlooktool_Automation_Triggered.json MIT; preserve source notices.