Skip to content
EmailReal-timeUpdated May 2026

Microsoft Outlook

Outlook inbox as a workflow trigger

Microsoft Outlook on Tiny Command is the inbox-as-workflow-source for organizations standardized on Microsoft 365. One trigger, Email Received, fires within seconds of a new message landing in a folder you've authorized (Inbox or any custom folder). Eight actions cover the email lifecycle: Send Email, Reply to Email, Create Draft, Delete Message, Move Message (to a different folder for organization), Get Message, List Messages, List Mail Folders. The integration authorizes via Microsoft Graph OAuth, Tiny Command's app registration handles consent in your Azure AD tenant. The connection respects Outlook's shared mailbox model: authorize as a user, and the workflow can access any mailbox that user has been granted delegate or shared access to. Common patterns: an Outlook Email Received with a specific subject pattern triggers a workflow that creates a Dynamics 365 contact, drafts a reply in Outlook for human review, and adds a Teams notification, all the Microsoft-365-native handoffs without leaving the ecosystem.

1trigger
8actions
≈ 2 minto set up
Freetier · no card
Triggers

Workflows start when Microsoft Outlook does.

1 real-time trigger, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven
Actions

Do anything Microsoft Outlook can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

ActionWhat it does
Create Outlook DraftCreates an email in the Drafts folder without sending. For "AI-generated reply suggestion → save as draft for user review" workflows.
Delete Outlook MessageSoft-deletes a message (moves to Deleted Items). For "auto-archive newsletters after reading" or "delete known spam patterns" inbox-management workflows.
Get Outlook MessageReturns a specific email with full body, attachments, headers. The standard lookup for "fetch this email captured upstream and process" workflows.
List Outlook Mail FoldersReturns the folder structure of the mailbox (Inbox, Sent, custom folders). Useful for resolving folder IDs at workflow setup.
List Outlook MessagesPaginated emails in a folder with filters. For "process unread emails matching pattern" batch workflows.
Move Outlook MessageMoves a message to a different folder. For "auto-file by sender or content classification" inbox-organisation workflows.
Reply to Outlook EmailReplies to a specific message preserving the thread. For "auto-acknowledge support emails" or "AI-generated reply approved → send" workflows.
Send Outlook EmailSends a new email from the connected mailbox. For "external event → send personalised email from my account" workflows.
Recipes

Pre-built Microsoft Outlook workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Microsoft Outlook once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Microsoft Outlook field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Microsoft Outlook integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Microsoft Outlook to Tiny Command?
Open the Tiny Command workflow builder, drop in a Microsoft Outlook node, and click Connect. Authorize Microsoft Outlook once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.
What Microsoft Outlook triggers does Tiny Command support?
Tiny Command supports 1 real-time Microsoft Outlook trigger, including "Outlook Email Received". Each trigger fires within seconds of the event happening in Microsoft Outlook.
What Microsoft Outlook actions can I run from a workflow?
8 Microsoft Outlook actions are available out of the box, covering email operations like "Create Outlook Draft". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.
Is the Microsoft Outlook integration real-time?
Yes. Outlook Email Received and every other Microsoft Outlook trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Microsoft Outlook rather than on a polling schedule.
Do I need to write code to use Microsoft Outlook with Tiny Command?
No. Every Microsoft Outlook trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Microsoft Outlook API endpoint directly.
How much does the Microsoft Outlook integration cost?
There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Microsoft Outlook integration itself has no per-app surcharge.
Related

More email apps people connect.

Same category as Microsoft Outlook, ordered by how often teams pair them. Hover the carousel to pause.

Do more with Microsoft Outlook.

Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.