Hi @ksrigane and welcome to the Quick Community!
To get started, you’ll need to setup the slack integration on your account, I would suggest reviewing the following documentation that walks through the process:
Since you’ve mentioned ‘slack connect for Amazon’, if you are an internal AWS team, I would suggest reaching out through an internal channel. As the community is a public facing forum, we would not have the ability to help with private account matters or have access to assist with providing this information.
Hi @ksrigane,
Apologies, I shared the wrong link (meant to share the below), no upgrade is needed. However the same note does apply that we would be able to assist with creating a new/corrected slack integration that has access to the proper channels. I would suggest reaching out internally to a manager who will have the ability to create new integrations within your account since we would not have access to assist.
Hope everything is well with you! Just checking back in since this thread hasn’t received a response in a while. Was Brett’s reply helpful to you or were you able to find a solution yourself in the meantime? Please help the community by marking this answer as “Solution” or following up in general within the next 3 business days!
Thank you for the follow-up. I did not have any solution on this issue. Seems like Quick is not stable, some times it says that it is connected to Slack and is able to send messages when i say so, but most of the times, it says that it has no connection with Slack.
I have stopped working with Quick Desktop because it is highly unreliable and it does not have right connectors to Slack as well. The above situation is about Quick web version and i had high hopes for it. However, its very unstable with Slack (like explained above).
Per the previous suggestion from Brett, i know no manager who has the ability to create new integrations within Quick. It would be great if you can help me with this or suggest me someone who is an expert. End of the day, all i need is an agent that should be able to connect with Slack, Outlook & Sharepoint and must be able to send scheduled alerts on Slack and Outlook.
Hi @ksrigane - totally understand the frustration with frequent logouts / inconsistent access behavior.
Anecdotally, that hasn’t been my experience with those connectors. I use the Slack / Email connectors and find they work well - which makes me think it’s an issue with the configuration of the current connector, not the connector itself. More likely than not, it’s not an issue on your end.
Based on the behavior you’re describing, one of the following might be happening:
Live updates to the connector are being made by the team managing it (could explain the forced occasional / unannounced logouts)
The connection isn’t scoped properly to your use case - especially relevant if it’s an internal / potentially sensitive channel
The connector isn’t being enabled in Quick Desktop: My experience has been you need to both have the connector set up at your account level, and have the connector enabled in Quick Desktop. I’d give this a try and verify that the Slack connector “should” be available
Multiple Slack connectors exist - if you haven’t already, I would check the available connectors in the Quick Console (online portal)
Quick sanity check: Slack connector’s “Connection Details” looks like in the online Quick Console (to check yours: Open Quick → Connectors → Slack → Summary → left pane)
Verify under “Connection Details” you are Signed in (assuming you are)
Verify Connector status = Ready
If you have a route to, I would open a ticket explaining the issue and attach a link to this thread.