Introduce search functionality in slack conversations.list & users.list method by name or any other method to search.

[Amark19]

Issues:

Currently, slack web-api only supports listing channels or users with these methods. But me & my team have faced a problem when our customer has a lot of channels/users present in their workspace. And currently we need to retrieve all channels/users by cursor based pagination but since channels/users are too huge & it requires a lot of pages to return the all data due to which API throws rate limit error.

Why do I need all list ?

I want my user to select only one channel among thousands/lakhs of channels present in their workspace so that user can send message using our service or can configure certain channel to automatically get daily updates. So, here although end goal is to let user search & select for the channel that they want to configure but to achieve this we need to fetch all data and that feels too counterintuitive.

If search functionality can be introduce this can be solved very easily or can suggest any other workaround here.

Packages:

Select all that apply:

• @slack/web-api
• @slack/rtm-api
• @slack/webhooks
• @slack/oauth
• @slack/socket-mode
• @slack/types
• I don't know

Requirements

Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

[WilliamBergamin]

Hi @Amark19 thanks for bringing this up 💯

I see that the conversations.list can be filtered by team_id, types and exclude_archived, expanding the filter options with name and users seems reasonable. I'll report the feature request internally, you can also bring this up to developers@slack.com

In the mean time, user tokens could be used to filter the conversations a specific user has access to

The "channels" returned depend on what the calling token has access to and the directives placed in the types parameter.

Have you tried obtaining the users access token and then using it to collect the conversations they have access to instead of collecting all the conversations in the workspace

Another alternative could be to keep a copy of the conversations in your app and have the app update the records when it receives a channel_created or channel_deleted event

[Amark19]

Hi @WilliamBergamin , thanks for showing up this quickly and for positive feedback !!

We have couple of workaround for this problem one of which is the one that you suggested but
Currently, our service does not keep such kind of data in DB or anywhere & for such smaller use case doing this seems bit overkill & costly for us.

Thanks !!