Outlook Trigger

Monitor an Outlook inbox and trigger workflows on new messages.

Overview

The Outlook Trigger starts a workflow when a new message arrives in a connected Outlook or Microsoft 365 mailbox. Spojit uses Microsoft Graph with the authorized account's OAuth grant to detect new messages and fires the trigger for each one that matches your filter.

It is commonly used for inbox-driven automations: routing customer messages into Slack or Front, extracting invoices and PDFs for downstream processing, classifying tickets with AI, or creating tasks in Monday.com from incoming requests.

What You Can Do

The Outlook Trigger watches a mailbox and exposes each new message to the workflow body:

new-message events - fires when a message arrives that matches your filter.
folder - optional Outlook folder (for example Inbox, Support) to scope which messages trigger the workflow.
filter - optional sender, subject, or category filter to narrow the trigger further.
from, to, cc, bcc, subject, received-date - standard email headers exposed to the workflow.
body-plain and body-html - the plain text and HTML versions of the message body.
attachments - an array of attachment metadata (filename, mime type, size) with content available to PDF, image, and CSV tools downstream.
conversation-id and message-id - identifiers useful for threading replies or deduplicating runs.

Authentication

The Outlook Trigger uses OAuth to access the mailbox. Spojit redirects you to Microsoft to sign in and authorize read access to mail. The grant works for personal Outlook.com accounts and Microsoft 365 work or school accounts. You can revoke access from your Microsoft account under Privacy -> Apps and services that can access your data.

Setting Up Your Connection

Go to Connections from the sidebar.
Click + Add Connection.
Search for Outlook Trigger and select it.
Click Connect to start the OAuth flow. Sign in to the Microsoft account whose mailbox you want to monitor and approve the requested scopes.
Optionally configure the folder to watch and a sender or subject filter.
Give your connection a name (for example "Sales inbox") and click Save.

Using the Trigger

Workflows that use this connection start on an email trigger node bound to the connection. Each new matching message fires one run of the workflow. Use {{trigger.subject}}, {{trigger.from}}, {{trigger.body-plain}}, and {{trigger.attachments}} in downstream nodes to act on the message contents.

Tips

Use Outlook inbox rules to move qualifying mail into a dedicated folder, then watch that folder for tighter scoping.
For attachment-driven workflows, branch on attachment count or mime type early so empty messages do not run the full pipeline.
Use conversation-id to deduplicate when long threads could otherwise fire the trigger multiple times.
Microsoft 365 tenants often enforce conditional access; if the connection fails, check with your IT admin that third-party app access is allowed.

Common Pitfalls

OAuth grants are tied to a single Microsoft account; switching mailboxes requires reconnecting.
Spojit polls the mailbox rather than pushing in real time, so triggers fire within a short delay, not instantly.
HTML-only messages may have an empty body-plain; use body-html and a text or AI node to normalize.
Shared mailboxes can require a different OAuth grant than the signed-in user; connect using the account that owns the mailbox.

Common Use Cases

For technical API details and field specifications, see the Outlook Trigger trigger documentation.