Outlook automations
Email · 1 integration · 2 workflow guides
Email and calendar automation with Outlook typically covers routing incoming messages to project tools, creating calendar events from form submissions, and syncing contacts across business systems. Most teams automate Outlook to reduce manual triage work and keep tools like Slack, CRM platforms, and ticketing systems in sync without human copy-paste. Choosing the right automation platform matters here because Outlook's API has strict per-mailbox quotas, short-lived webhook subscriptions, and an ongoing deprecation cycle that affects how reliably different tools connect.
What it costs to automate Outlook
Platform pricing at different volumes. Annual billing shown.
| Platform | Free tier | 100 tasks/mo | 1K tasks/mo | 10K tasks/mo |
|---|---|---|---|---|
| Zapier | 100 tasks/mo | Free | $69/mo | $69+/mo |
| Power Automate | 750 runs/mo | Free | $15/mo | $15/mo |
| Make | 1,000 credits/mo | Free | Free | $10.59/mo |
| Pipedream | 100 credits/mo | Free | $29/mo | $79/mo |
| n8n | Yes | $20/mo | $20/mo | $50/mo |
Outlook integrations
Each page compares all five platforms for that pair.
Popular Outlook workflow guides
Step-by-step setup instructions for specific automations.
How to Send Outlook Emails to Slack with Zapier
Automatically posts a Slack channel message whenever a new email arrives in Outlook, optionally filtered by sender, subject keyword, or folder.
How to Send Outlook Email Alerts to Slack with Make
Automatically posts a Slack channel message whenever a new email arrives in Outlook, filtered by sender, subject, or folder.
Outlook triggers & actions by platform
Which capabilities each platform supports for Outlook.
| Capability | Pipedream | Zapier | Power Automate | Make | n8n |
|---|---|---|---|---|---|
| Triggers | |||||
| App Event Source | ✓ | — | — | — | — |
| Calendar Event Created | — | ✓ | — | — | — |
| Calendar Trigger | — | — | — | — | ✓ |
| Email Trigger | — | — | — | — | ✓ |
| HTTP Webhook | ✓ | — | — | — | — |
| New Email | — | ✓ | — | — | — |
| Schedule | ✓ | — | — | — | — |
| Scheduled flow | — | — | ✓ | — | — |
| Watch Calendar Events | — | — | — | ✓ | — |
| Watch Emails | — | — | — | ✓ | — |
| When an item is created | — | — | ✓ | — | — |
| Actions | |||||
| Send Message | ✓ | — | — | — | ✓ |
| Create a record | — | — | ✓ | — | — |
| Create Channel | — | — | — | — | ✓ |
| Create Message | — | — | — | ✓ | — |
| Create Record | ✓ | — | — | — | — |
| Custom Code Step | ✓ | — | — | — | — |
| Get rows | — | — | ✓ | — | — |
| HTTP Request | ✓ | — | — | — | — |
| Send a notification | — | — | ✓ | — | — |
| Send an email | — | — | ✓ | — | — |
| Send Channel Message | — | ✓ | — | — | — |
| Send Direct Message | — | ✓ | — | — | — |
| Update Channel Topic | — | — | — | ✓ | — |
Things to know about automating Outlook
Webhook Subscriptions Expire Fast
Outlook change notification subscriptions expire after a maximum of 4,230 minutes — just under 3 days. Any automation platform (Zapier, Make, n8n, Power Automate, Pipedream) must actively renew these subscriptions or your email triggers silently stop firing with no error surfaced to you.
Rate Limits Are Per-Mailbox
The Graph API allows 10,000 requests per 10-minute window per app ID and mailbox combination, with a hard cap of 4 concurrent requests at any moment. This means high-volume workflows hitting a single mailbox will throttle independently from other mailboxes — but a single busy automation can still exhaust that quota alone.
EWS Shuts Down October 2026
Exchange Web Services will be fully blocked for Exchange Online starting October 1, 2026. If any of your automations — or the platforms running them — rely on EWS rather than Microsoft Graph, they will stop working entirely and require migration before that date.
App-Only Auth for Unattended Workflows
Delegated permissions only allow subscribing to the signed-in user's own mailbox, which breaks multi-mailbox and background automation scenarios. For daemon-style workflows that run without a signed-in user, application permissions with admin consent are required — a setup step that often catches teams off guard in enterprise tenants.
429 Errors Can Lie
A documented real-world behavior with the Graph API is that POST requests sometimes return a 429 error while the underlying operation still succeeds. Workflows that retry on 429 without deduplication logic — common in default Zapier and Make configurations — can create duplicate emails, calendar events, or records as a result.
Token Expiry Breaks Long Jobs
Access tokens issued by the Microsoft identity platform last 60–90 minutes by default and cannot exceed 24 hours even with a token lifetime policy. Refresh tokens last up to 90 days but are immediately invalidated by password resets — a real risk in enterprises with 90-day rotation policies, requiring re-authentication across Zapier, Make, n8n, Power Automate, or Pipedream.
What breaks at scale
The Graph API enforces a hard limit of 10,000 requests per 10-minute window per app ID and mailbox combination, with only 4 concurrent requests allowed at any time. At this threshold you will receive 429 responses — but critically, some of those 429s may still correspond to operations that succeeded on the server side, meaning any retry logic without deduplication will create duplicate emails, calendar entries, or forwarded messages. Microsoft's own documentation acknowledges undocumented sub-limits that can trigger 429s well below the published ceiling, making this failure mode unpredictable and hard to debug.
Outlook Graph subscriptions expire after 4,230 minutes and will silently lapse if not renewed — and once dropped, missed notifications are permanently unrecoverable. In practice, n8n users have reported automations that work reliably for over a month before renewal failures cause triggers to stop firing entirely, requiring manual restart to resume. Any platform — Zapier, Make, n8n, Power Automate, or Pipedream — that doesn't surface subscription renewal failures as visible errors leaves you exposed to silent data loss where incoming emails or calendar changes go unprocessed with no alert.
Refresh tokens for Microsoft Graph have a default lifetime of 14 days and a maximum of 90 days, but are immediately invalidated the moment a user's password is reset or their account is modified. In enterprises with mandatory 90-day password rotation, every rotation cycle can silently break any automation credential stored in Zapier, Make, n8n, Power Automate, or Pipedream that uses delegated (user-based) OAuth. The token cannot be exported or transferred between platforms, so re-authentication must happen manually inside each tool — and workflows fail silently until someone notices, making app-only authentication a much safer choice for production automations.
Frequently asked questions
Which automation platform works best with Microsoft Outlook?
Power Automate has the deepest native Outlook integration since both are Microsoft products, making it the lowest-friction option for most Microsoft 365 tenants — especially for calendar and email triggers. Zapier and Make both offer solid Outlook connectors for simpler workflows, while n8n and Pipedream give more control over Graph API calls and token management for custom or high-volume use cases. The right choice depends on whether you need IT-managed enterprise controls (Power Automate), low cost at volume (Make), or code-level flexibility (n8n, Pipedream).
Why do my Outlook automation triggers stop working after a few days?
Outlook webhook subscriptions through the Microsoft Graph API expire after a maximum of 4,230 minutes — roughly 3 days — and must be explicitly renewed before they lapse. If the automation platform you're using (n8n is a known offender here, but the issue can affect any tool) doesn't handle subscription renewal reliably, triggers silently stop firing and dropped notifications cannot be recovered. Check your platform's documentation for how it manages Graph subscription renewals, and consider building a monitoring alert if triggers go quiet unexpectedly.
How much does it cost to automate Outlook at scale with Zapier vs Make?
Zapier's pricing is task-based and multiplies across steps — a 5-step workflow triggered 10,000 times per month costs roughly $99/month on the Professional plan, and each step counts as a separate task. The same volume on Make costs approximately $10.59/month because Make charges by operations rather than per-step task counts. For high-frequency Outlook automations like processing every incoming email, that pricing gap becomes significant quickly, making Make, n8n, Power Automate, or Pipedream worth evaluating before committing to Zapier at volume.
Do I need admin consent to automate Outlook with the Microsoft Graph API?
For delegated permissions — where the automation acts on behalf of a signed-in user — admin consent may or may not be required depending on the specific scopes requested. However, for application permissions used in background or multi-mailbox automation (the type required by most production workflows on Zapier, Make, n8n, Power Automate, or Pipedream), admin consent from an authorized Azure AD administrator is always required. Any time you change the permissions configured in your app registration, the admin must reconsent before the new permissions take effect.