Skip to main content
Best answer

Getting Error "Requires scope `reactions:read`" when trying to use Slack API step


I’m trying to create a Zap that does the following -- When a message is posted to a channel, and no one reacts to it for 60 minutes, then reply in the thread tagging someone.

From what I can tell so far, I need to use a Slack API step to get reaction counts based on this - 

 

However, I get the following error when I try to test the step -- “

Failed to create a http request in Slack

Raw request failed. HTTP Status: 200. Problem executing your request: This is a new feature! To take advantage of it, you'll need to reconnect your auth. Requires scope `reactions:read`. This error could also be generated because you are trying to pull objects (Mention, Reaction, etc) from a DM or private channel.”

 

Initially, I was trying this with a private channel. But it isn’t even working with a public channel where I am the Slack Channel Manager. 

 

What am I doing wrong?

Best answer by SamBBest answer by SamB

Hi there ​@karthikz 👋

You’re not doing anything wrong! I was able to reproduce that same error when using Slack’s API Request action. It seems that something has since changed to the authentication scopes the API Requests use. 🤔 

I can see there’s a feature request open for to increase the scopes so I’ve added your vote to that which will help to increase its priority. I can’t make any promises as to when the additional permission scopes will added but we’ll be sure to email you as soon as they are.

That said, I tried setting up a Custom Action to get the reactions it worked so I’d recommend using that approach for now. 

I used the a prompt of “Want to make a request to Slack's https://slack.com/api/reactions.get endpoint. Need to specify the Channel ID and Timestamp of the message” and the Copilot then generated a custom action that I could then use in a Zap:

abcfd3b0817b1d9f7dcd5bba343c3b73.png

 

Once you Publish the custom action you’ll then be able to select it from the Custom actions tab in your Zap:
e1753ccb5e77668c694fb659de966c22.png

From there you’d just need to select the Channel and the Timestamp for the message you want the Zap to get the reactions for:
ffbd335d2bd3aecaa2e610440af1708c.png
f6acd8f83b766fa9fb995cac3a3fe487.png
 

You can learn more about custom actions here: Create a custom action.

Hope that helps to get things up and running in the meantime. If you run into any trouble setting up that custom action just let me know! 🙂

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

2 replies

SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7396 replies
  • Answer
  • February 5, 2025

Hi there ​@karthikz 👋

You’re not doing anything wrong! I was able to reproduce that same error when using Slack’s API Request action. It seems that something has since changed to the authentication scopes the API Requests use. 🤔 

I can see there’s a feature request open for to increase the scopes so I’ve added your vote to that which will help to increase its priority. I can’t make any promises as to when the additional permission scopes will added but we’ll be sure to email you as soon as they are.

That said, I tried setting up a Custom Action to get the reactions it worked so I’d recommend using that approach for now. 

I used the a prompt of “Want to make a request to Slack's https://slack.com/api/reactions.get endpoint. Need to specify the Channel ID and Timestamp of the message” and the Copilot then generated a custom action that I could then use in a Zap:

abcfd3b0817b1d9f7dcd5bba343c3b73.png

 

Once you Publish the custom action you’ll then be able to select it from the Custom actions tab in your Zap:
e1753ccb5e77668c694fb659de966c22.png

From there you’d just need to select the Channel and the Timestamp for the message you want the Zap to get the reactions for:
ffbd335d2bd3aecaa2e610440af1708c.png
f6acd8f83b766fa9fb995cac3a3fe487.png
 

You can learn more about custom actions here: Create a custom action.

Hope that helps to get things up and running in the meantime. If you run into any trouble setting up that custom action just let me know! 🙂


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7396 replies
  • February 14, 2025

Hey ​@karthikz 👋

Just following up here to confirm that feature request has been closed. In case you missed the email notification that was sent here’s the important details from it:

“The Make API Request action is in beta and not all scopes for all endpoints in the Slack app can be supported. A recent update to the integration may mean that previously supported scopes can no longer be included as available in Make API Request calls to the Slack API. To resolve this issue, you'll either want to select from existing Slack triggers/ or actions. Or, you will be able to restore those calls by building a custom action as detailed here: https://help.zapier.com/hc/en-us/articles/16276574838925-Custom-Actions-in-Zapier

That being the case, anyone running into that "Requires scope `reactions:read`" error will need to use the custom action, as outlined in the workaround I shared earlier.

Happy to help if anyone runs into trouble setting that up. In the meantime, happy Zapping! ⚡