So it looks like the files:read permission is in the Slack x Zapier integration but…

 

Hi ​@Philippe - Joy 

As per the error message you are receiving, I would suggest you go to “App Connection” and look for the Slack connection, click on the 3 dots on the right hand side and choose “Reconnect”. Have you tried doing that?

Hello ​@MohSwellam 

Yeah, I tried it and it did not work unfortunately...

An alternative would be to create a new connection, or have you already tried that? And when you do that, are you checking all the boxes if the scope is optional?

I already tried it too, and there are no boxes to check as the scope is not optional.

I might be doing something really wrong but I strongly believe the integration is not working the way it has been designed to.

Any way that we can make sure the Zapier integration of Slack is indeed including files:read and that the description is not including infos from previous versions that changed since then ?

Hi ​@Philippe - Joy,

Welcome to the Community.

Check and update the app's permissions to ensure your Slack integration with Zapier works smoothly. Visit the Slack API site, go to your app's OAuth & Permissions, and confirm that scopes like files:read are included. If not, add them and reinstall the app in your Slack workspace. Then, in Zapier, reconnect the Slack app under My Apps to apply the changes. Finally, test your Zap to confirm it's working correctly and update any outdated descriptions to reflect the current setup.

If you have any further questions or need additional guidance, feel free to ask. We're here to help.

Hi ​@Philippe - Joy this was driving me nuts as well, and I figured out a workaround over the weekend. It’s a long thread, but the solution is in this post:

Essentially, you’re right, the OAuth connection doesn’t have the files:read scope, and an API action from the Slack integration won’t work. What I stumbled on was the fact that, for some reason, if you build a Custom Action, it seems to have higher permissions than the regular Slack integration and API action. So I created a Custom Action to convert the Slack file to public, pass the public URL to another step, and when I’m done with it, I convert the file in Slack back to private.

Let me know if you have any questions - it’s been working smoothly for me for the past few days.

I’m going to look into today, and I’m super hyped by the fact that this a very clever workaround. Will let you know but thank you so much for your time and the thorough thread!

Hello JammerS,

The issue really is not on my side, the OAuth does not have the permission it is supposed to have. I think the technical should be looking into it to be honest.

Best!
Philippe.

Hi ​@Philippe - Joy,

Thanks for bringing this to our attention. You're facing an OAuth permissions issue that is affecting your Zap. To help resolve it, try re-authenticating the app and ensuring all necessary permissions are granted. Also, check the app's settings to confirm it allows access. Please contact our Zapier support team, and send them any error messages or logs you can share will help them investigate faster. We appreciate your patience and are committed to getting this resolved quickly.

Feel free to reach out if you have any questions or need further assistance.

Hello Jammer,

As I said previously, I already did it and it probably is not on my side but on the Zapier x Slack integration...