add slack thread reader tool #1967
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@sudhanshug16 is attempting to deploy a commit to the Sim Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
Greptile OverviewGreptile SummaryThis PR adds a new Slack thread reader tool that fetches complete thread context when a Slack bot is mentioned in a thread. The implementation introduces the The changes include: creating the core tool implementation ( Important Files Changed
Confidence score: 3/5
Sequence DiagramsequenceDiagram
participant User
participant SlackBlock
participant SlackThreadReaderTool
participant SlackAPI
User->>SlackBlock: "Configure thread reader with channel and thread_ts"
SlackBlock->>SlackBlock: "Validate authentication method (OAuth/Bot Token)"
SlackBlock->>SlackBlock: "Set operation to 'read_thread'"
SlackBlock->>SlackThreadReaderTool: "Execute with parameters"
SlackThreadReaderTool->>SlackThreadReaderTool: "Build URL with channel, thread_ts, limit, cursor"
SlackThreadReaderTool->>SlackAPI: "GET /api/conversations.replies"
SlackAPI-->>SlackThreadReaderTool: "Return thread messages (root + replies)"
SlackThreadReaderTool->>SlackThreadReaderTool: "Transform response: map messages with ts, text, user, files"
SlackThreadReaderTool->>SlackThreadReaderTool: "Extract pagination info (has_more, next_cursor)"
SlackThreadReaderTool-->>SlackBlock: "Return thread data with messages array"
SlackBlock-->>User: "Provide thread_ts, messages, has_more, next_cursor"
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
+82
to
+83
| const limit = params.limit ? Number(params.limit) : 20 | ||
| url.searchParams.append('limit', String(Math.min(limit, 15))) |
Contributor
There was a problem hiding this comment.
logic: Inconsistent limit handling - parameter description says max: 100 but implementation caps at 15
Suggested change
| const limit = params.limit ? Number(params.limit) : 20 | |
| url.searchParams.append('limit', String(Math.min(limit, 15))) | |
| const limit = params.limit ? Number(params.limit) : 20 | |
| url.searchParams.append('limit', String(Math.min(limit, 100))) |
Should the maximum limit be 100 as documented or 15 as implemented?
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/sim/tools/slack/thread_reader.ts
Line: 82:83
Comment:
**logic:** Inconsistent limit handling - parameter description says max: 100 but implementation caps at 15
```suggestion
const limit = params.limit ? Number(params.limit) : 20
url.searchParams.append('limit', String(Math.min(limit, 100)))
```
Should the maximum limit be 100 as documented or 15 as implemented?
How can I resolve this? If you propose a fix, please make it concise.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds a tool for slack to read a thread given the thread_ts. Useful when the slack bot is mentioned in a thread and we want the context of the thread.
Fixes #(issue)
Type of Change
Testing
Manually tested the tool using a thread in our company slack. Output showed the parent plus every reply and has_more:false, confirming the code paths and response mapping.
Checklist