Good afternoon Redash Support community
Our company has been using your products to help us visualise information from our database storage in a cloud relational-databse product. Redash has been doing well with our in-browser use and has given us many useful insights, but we would like to look at integrating the Redash application into our Slack as we see more of our analysts and some engineers use it.
To that end, we are using the same information from the locally hosted instance of Redash on our cloud-providers’ servers, and have set the Redash Slack Integration up within a freshly-made testing slack workspace with the requested information of a:
 Workspace URL =
Also, [For the purposes of this post, all * = /] (Otherwise, I get a “disallowed” error about a number of links(!) in this post.)
 API Key from
*users*me#apiKey - AaAaaA0aAa0A0a0AaaaaaAAaAa0AA0aaa00A0a0a (preserving the uppercaselowercase, letternumber distinction of my account’s key)
And whether or not I regenerate my API key immediately after the configuration or not, I still receive nothing past
One moment, bringing preview of: (Workspace URL)*queries*1430. for the command
/redash (Workspace URL)*queries*1430 and again, no visualisation results from the bot at all after pasting a link, such as
(Workspace URL)*queries*1430, into a channel.
Similarly, looking for the query by the name of the query, such as the command
/redash query name from the title bar of my query' only shows me a never resolved error OK, looking for a query that matches - query name from the title bar of my query.`
This holds true whether I do it as the workspace owner, or a second account I created as a workspace user in Slack, and after I have added the Redash bot to the channel in question (thanks to Jesse of Redash for suggesting this – but it unfortunately did not fix the issue).
As this doesn’t match what your documentation implies from the previously linked page, we would like to ask for clarification into the following details.
(1) Do the permissions scoped to this bot look correct? (Attaching two images.)
Should these permissions be changed at all to improve the bot’s integration?
(2) Does the API key need to be an active API key? Does it need to be of a certain user in Redash, such as one with administrative access or some other level of permissions?
(3) How is the API key used? Is it to set up the initial integration, or is it employed every time that someone calls the app from then onwards?
(4) Why do the documentation images show
redashbot BOT instead of
Redash APP? Is this part of the problem I am seeing right now?
(5) Is there any other guidance that could be given to getting the BOT to correctly integrate with our workspace? For now, not being able to integrate it in a cleanly created development environment is a blocker for us to try to integrate the Redash app for Slack to our production Slack workspace.
Would like help from community members and Redash staff members to verify the above. Thank you!