This topic was automatically generated from Slack. You can find the original thread here.
I’m having some trouble with a deployed trigger. It doesn’t seem to generate any events when I would expect it to, and attempts to update the trigger fails with this error:
{“error”:“Unexpected error, please reach out to our team at Support - Pipedream”}
What do you need from me? The trigger ID is dc_dAu7GKR.
Ah I see it’s a Slack trigger with your own OAuth, right? Unfortunately Slack triggers only work with Pipedream OAuth right now.
Wait, so does that mean that if I want to consume Slack events, then I have to accept that our users get a Pipedream bot instead of a branded bot in their workspace?
Honestly, that is pretty unacceptable.
Unfortunately yes that is the case right now. FYI when sending messages you can customize the Bot’s username and icon.
The way Slack handles event subscriptions is unfortunately fairly unique and requires some pretty complex handling within the Pipedream platform side in order to support listening for events, which is the core of that specific constraint. When you create an OAuth client in Slack, you have to manually define a single webhook URI where you want them to send all events. Nearly all other APIs that support webhooks let you programmatically register webhooks on behalf of end users, rather than using a single URI.
Oh, that’s good news. Thank you - is there a documentation link for setting up the bot’s username and icon?
Check out the configurable props for the relevant actions.