Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-21 01:25:28 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #3705] [FEAT]: Slack Data connector #2386

New Issue
Open
opened 2026-02-22 18:29:27 -05:00 by yindo · 2 comments
yindo commented 2026-02-22 18:29:27 -05:00
Owner
Copy Link
Copy Source

Originally created by @sherman-yang on GitHub (Apr 23, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3705

What would you like to see?

[FEAT]: can connect Slack channells(by config), pull all messages into Vector database.

Originally created by @sherman-yang on GitHub (Apr 23, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3705 ### What would you like to see? [FEAT]: can connect Slack channells(by config), pull all messages into Vector database.
yindo added the enhancementfeature request labels 2026-02-22 18:29:27 -05:00
yindo commented 2026-02-22 18:29:27 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Apr 23, 2025):

Would a Slack agent skill be better? Data in the vector db is typically static and not real time. If you had an agent to query/find information in a channel that would like serve this need better since updating the slack information would have to be done at regular intervals to remain current?

We do have an automatic refresh process in this experimental feature, so its not impossible - i just wonder what the best form factor is here for your use-case

@timothycarambat commented on GitHub (Apr 23, 2025): Would a Slack agent skill be better? Data in the vector db is typically static and not real time. If you had an agent to query/find information in a channel that would like serve this need better since updating the slack information would have to be done at regular intervals to remain current? We do have an automatic refresh process [in this experimental feature](https://docs.anythingllm.com/beta-preview/active-features/live-document-sync), so its not impossible - i just wonder what the best form factor is here for your use-case
yindo commented 2026-02-22 18:29:27 -05:00
Author
Owner
Copy Link
Copy Source

@sherman-yang commented on GitHub (Apr 24, 2025):

sounds great! I don't know there is a Slack agent skill, could you tell me where it is? thanks a lot

@sherman-yang commented on GitHub (Apr 24, 2025): sounds great! I don't know there is a Slack agent skill, could you tell me where it is? thanks a lot
yindo changed title from [FEAT]: Slack Data connector to [GH-ISSUE #3705] [FEAT]: Slack Data connector 2026-06-05 14:46:16 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2386
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?