Skip to main content
Best answer

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

  • February 4, 2025
  • 1 reply
  • 13 views

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?

1 reply

SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7274 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! 🙂