openclaw - 💡(How to fix) Fix Slack: message read with threadId doesn't return thread replies [1 participants]

Fix Plan

To fix the issue, we need to modify the Slack plugin to use the conversations.replies API when the threadId parameter is provided. Here are the steps:

• Update the Slack plugin to check for the presence of the threadId parameter in the message read action.
• If threadId is present, use the conversations.replies API instead of conversations.history.
• Pass the channelId and threadId as parameters to the conversations.replies API.

Example code snippet:

if action == 'read' and 'threadId' in params:
    # Use conversations.replies API
    url = f'https://slack.com/api/conversations.replies'
    params = {
        'channel': params['channelId'],
        'ts': params['threadId']
    }
    response = requests.get(url, params=params, headers=headers)
else:
    # Use conversations.history API
    url = f'https://slack.com/api/conversations.history'
    params = {
        'channel': params['channelId'],
        'limit': params['limit']
    }
    response = requests.get(url, params=params, headers=headers)

Verification

To verify the fix, call the message read action with the threadId parameter and check if the response includes the thread replies. You can use the same example provided in the issue body:

{
  "action": "read",
  "channel": "slack",
  "channelId": "C0AL7KZ75TP",
  "threadId": "1773368311.447129",
  "limit": 20
}

The response should include the thread replies instead of the channel messages.

Extra Tips

• Make sure to handle any errors that may occur when calling the conversations.replies API.
• Consider adding logging to track any issues that may arise from the updated code.
• Test the fix thoroughly to ensure it works as expected in different scenarios.