This topic was automatically generated from Slack. You can find the original thread here.
I’d also like to know if there’s a way I can connect Pipedream to Slack so that the only permissions it gets are to a single channel. I’m trying to build an automation for my agency, but they are not likely to want a 3rd-party integration to have access to the entire account, which contains a lot of sensitive information.
You might check your Slack administration settings to confirm. Some Slack plans may allow such custom settings. But as far as I know, the answer is no. I don’t think Slack allows public apps like this to be installed to a specific channel.
Are you comfortable building your own Slack app / bot? It’s not ideal, but you can add those credentials via our Slack Bot app, or as an environment variable, and you can pass that token to the Slack Node.js Slack client. The limitation here is that you can’t use the pre-existing Slack triggers / actions with a custom Slack bot.
The ideal solution — which is on our backlog — is to let you create your own Slack app and enter the client credentials in Pipedream. Then you’d have full control over the Slack app, and you could use all of our pre-existing triggers / actions.
Let me know if the custom Slack Bot route would work for now.
Hey - I’ve never build a custom Slack bot before, but I’m up for that challenge if it’s not too gargantuan of a task!
We actually published most of the same triggers and actions the normal Slack app uses, to support the Slack Bot app as well!
If that method will allow me to set bot permissions restricted only to a single channel, then that should work.
Oh sweet Danny, that’s good to know
What I don’t want to do is deploy it to my own servers and deal with all the security headaches, hence why I still want to use Pipedream haha
Would probably also make a useful tutorial on TF Explains
yeah in this case, you’ll still have to install the private app to the workspace, but then you can add the app / bot to specific channels only. You’ll have to look at the docs on the Slack app permissions to confirm exactly what the app can access (they also have some good details in the app builder UI, at Slack API: Applications | Slack). Might be good to ask Slack directly re: the permissions issue. I believe it may depend on what permissions you add to the app / bot itself, e.g. search permissions are global but other permissions can be scoped to only the channels the bot is a part of.
I have to look at the docs every time we build a new Slack bot ourselves 
Gotcha. In this case I think it should be pretty easy to restrict the permissions - our Talent team simply wants a channel where they can send tasks to Notion
So literally all I need are permissions for the bot to access that one channel and read the messages sent there, maybe write as well so it can sent confirmations or errors
So to confirm: I still need to wait for Pipedream to add this capability right?
I don’t believe you can use the Pipedream Slack app in this manner (but I would consult with Slack to confirm, since there may be app permissions options I’m not aware of on your workspace).
But you should be able to create your own Slack Bot, and add your bot token in the Slack Bot connected account in Pipedream. Then you should be able to run workflows with those bot credentials in Pipedream.
Does that work?
Ah, this? https://pipedream.com/apps/slack-bot
Ah, I see what you were describing above. This already exists, but just doesn’t have access to the pre-defined triggers. That’s fine with me!
Exactly right