Outlook Trigger
Trigger workflows when new emails arrive in Microsoft Outlook.
Overview
Start workflows automatically when new emails arrive in your Microsoft Outlook inbox. Supports filtering by sender, subject, importance, and attachment presence. Uses the Microsoft Graph API to poll for new messages.
Getting Connected
Before using the Outlook Trigger, you need to create a Microsoft Outlook credential:
- Go to Dashboard → Credentials → Add Credential
- Select Microsoft Outlook from the credential type list
- Give it a name and click Connect Microsoft Outlook
- Sign in with your Microsoft account and grant the requested permissions
- Once connected, select this credential in the Outlook Trigger config panel
Works with personal Outlook.com accounts and Microsoft 365 work/school accounts. Tokens refresh automatically.
Configuration
- Outlook Account — select a connected Microsoft Outlook credential
- Folder ID — optional; specify a folder ID to watch instead of the default Inbox
Filters
Narrow which emails trigger the workflow:
- From Address — only trigger for emails from a specific sender (e.g.,
orders@example.com) - Subject Contains — only trigger when the subject line contains specific text
- Importance — filter by High, Normal, or Low importance
- Only messages with attachments — skip emails that have no attachments
Available Trigger Data
The trigger makes the following variables available to downstream nodes:
{{$trigger.message.from}}— sender email address{{$trigger.message.to}}— recipient email address{{$trigger.message.subject}}— email subject line{{$trigger.message.body}}— email body content{{$trigger.message.receivedAt}}— received timestamp{{$trigger.message.id}}— unique message ID{{$trigger.message.hasAttachments}}— whether the email has attachments
Example: Route Support Emails
Automatically process incoming support requests:
- Set From Address to
support@yourdomain.com - Add a Condition node to check
{{$trigger.message.subject}}for keywords like “urgent” - Route to an AI Prompt node to classify and auto-respond, or a HighLevel node to create a CRM contact
Troubleshooting
- No emails appearing in test — ensure the connected account has recent emails in the Inbox (or the specified folder). The test fetches the 5 most recent messages.
- Trigger not firing — verify the credential is still connected. Tokens refresh automatically, but if the refresh token is revoked, you'll need to reconnect.
- Filters too restrictive — try removing filters to confirm the trigger works, then add them back one at a time.