Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

  • Home
  • Get Help
  • How Do I
  • How do I prevent the Zap from re-triggering a Slack message when an Outlook email in shared mailbox is archived?

I have a trigger set up to send a slack message to a channel when an e-mail arrives in a shared mailbox in Outlook. The trigger works just fine for when the email is new, but it triggers again when an e-mail is archived by someone. Is there a way to stop this second trigger from happening?

Hi there @TanjaBergen,

Welcome to the Community! 🎉

I did some digging into this, and it seems like this is a known bug with the Microsoft Outlook integration. Specifically, when you move an email to a different folder or delete a message, a new ID is generated. This ID is what we deduplicate on, and since it is a new ID, the Zap triggers again. Our team is aware of the issue and is working on a fix. I've added your email address as another affected user. That does a few things:

  • Bring this to the attention of the integration developers
  • Help track and prioritize fixes
  • Allows us to notify you via email if/when this is fixed

Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.

There is a workaround that you can use, which is to use a filter action for the parentFolderId value by adding a (Text) Contains field. Use the ID for the Zap run when it first arrives in the Inbox.

Hopefully, this helps.

Terms & Conditions