Microsoft Office: New emails won't trigger Zap
- Tables
-
Product updates
Product updates: January 2023 Product updates: March 2023 Product updates: February 2023 Product updates: April 2023 Product updates: May 2023 Product updates: June 2023 Product updates: July 2023 Product updates: August 2023 Product updates: September 2023 Product updates: October 2023 Product updates: November 2023 Product updates: December 2023 Product updates: January 2024 Product updates: February 2024 Product updates: March 2024 Product updates: April 2024 Product updates: May 2024 Product updates: June 2024 Product updates: July 2024 Product updates: August 2024 Product updates: September 2024 Product updates: October 2024 Product updates: November 2024 Product updates: December 2024 Product updates: January 2025 Product updates: February 2025 Product updates: March 2025 Product updates: April 2025 Product updates: May 2025 Product updates: June 2025 Product updates: July 2025 Product updates: August 2025
- Zaps
- Your Zapier account
- Interfaces
- Canvas
- Chatbots
- Getting started
- Agents
- MCP
- Built-in tools
- Lead Router
- Apps
Table of Contents
Symptoms
When using Microsoft Outlook's New Email trigger in your Zap, the Zap does not run. Your Zap is turned on, but there is no corresponding Zap run in your Zap history.
Causes
This happens for a few reasons:
- The sender and receiver of the email are the same.
- The sender and receiver's domains are the same, and the receiver's email address is a shared inbox. The Zap will not trigger for emails sent to a shared inbox with the same domain as the sender's address.
- The New Email trigger can only trigger on up to 50 emails per polling interval.
How to fix it
To fix this:
- Check the sender's email isn't the same as the email as the connected app account (receiver's email) in your Zap.
- Send emails from an address with a different domain to your connected app account.
- For Zapier paid plans, you can adjust the polling interval between 1 and 15 mins.