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
  • Troubleshooting
  • Slack error: "This is a new feature! To take advantage of it, you'll need to reconnect your auth. Requires scope `im:history`"

This post was split from the topic: 

@chanelle, thank you for the detailed post. However, in the latest Slack integration available in Zapier, I don’t the webhook URL.

This is the error that I see when I’m trying to set it up.

Error code: Error while retrieving: This is a new feature! To take advantage of it, you'll need to reconnect your auth. Requires scope `mpim:history`. This error could also be generated because you are trying to pull objects (Mention, Reaction, etc) from a DM or private channel.

Appreciate any assistance that you can share. Thanks.

Hi @chandra2k6, welcome to the Community! 🎉

I’m so sorry we missed your message previously. I’ve moved it out into a brand new topic now so we can address it separately here. 🙂

I did some checking and found bug report where that error is occurring when attempting to load test records in the New Mention Slack trigger. So I’ve gone ahead and added you to that. I can’t make any promises as to when it will be resolved but we’ll definitely reach out via email once it is.

It’s been noted on the bug report that the error occurs when the it attempts to load a mention of the highlight word from within in a private channel. So as a workaround can you try the following steps:

  • Post a message in a public channel with the specific ‘highlight word’ that should trigger the Zap.
  • Then in the Zap, immediately try to load a new test record from Slack.


It may take a few attempts depending on how many instances there are of the highlight word in your Slack workspace but should eventually load in a sample without error.

Can you give that a try and let me know how you get on?

Reply


Terms & Conditions