Skip to main content
Best answer

Slack error: "This is a new feature! To take advantage of it, you'll need to reconnect your auth. Requires scope `im:history`"

  • August 30, 2024
  • 1 reply
  • 139 views

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.

Best answer by SamBBest answer by SamB

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?

View original
Did this topic help you find an answer to your question?

1 reply

SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7442 replies
  • Answer
  • September 19, 2024

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?