Hi All. The langchain-fleet Slack Bot needs to be configured as ‘Publicly Distributed’ (see example above). - RT
Hi,
Could you please provide the following info to help us better triage this:
- What are you trying to do with Slack tools
- Which environment is this (SaaS? which one eg. AWS)
- Tenant ID
Hi Aaryan,
The agent produces an output. That output needs to be written/published to a Slack channel.
The url should answer the question about the environment and the org-id …
Let me know, if you have any other questions.
Regards … Roland
Thanks for the clarification. We were in the process of authorizing our AWS Slack app. Slack tools work for me on a personal account. Could you please try again and let us know if the issue still persists.
No. The connect still fails. Here is the url that langsmith is using for the connect …
https://ailtir.slack.com/oauth?client_id=4518649543379.10766452350054&scope=chat%3Awrite+channels%3Aread+channels%3Ahistory+groups%3Aread+groups%3Ahistory+im%3Aread+im%3Awrite+im%3Ahistory+mpim%3Aread+mpim%3Ahistory+users%3Aread+users%3Aread.email&user_scope=&redirect_uri=https%3A%2F%2Faws.smith.langchain.com%2Fhost-oauth-callback%2Fslack-fleet&state=gn-iDSkxtc8vgjgLOWw-pnWBpFiUJKgV4lFQlCvOpH8&granular_bot_scope=1&single_channel=0&install_redirect=&tracked=1&user_default=0&response_type=code&team=
The client_id of the slack-app is …
4518649543379.10766452350054
Can you double check that the Slack App with this id has a Distribution Status of Publicly Distributed?
Regards … Roland
Note: Not sure, if this is related and/or makes a difference, but the url looks truncated.
We are still waiting for the AWS App to be authorized. Will post an update once I have confirmation on the same.
