# Send Slack messages into threaded replies

**URL:** <https://discuss.bitrise.io/t/send-slack-messages-into-threaded-replies/19940>\
**Category:** Released\
**Tags:** step, slack\
**Created:** [April 26, 2022, 8:05pm UTC](https://discuss.bitrise.io/t/send-slack-messages-into-threaded-replies/19940 "2022-04-26T20:05:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![liam-nichols](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/liam-nichols/32/4362_2.png) [@liam-nichols](https://discuss.bitrise.io/u/liam-nichols)\
**Post date:** [April 26, 2022, 8:05pm UTC](https://discuss.bitrise.io/t/send-slack-messages-into-threaded-replies/19940/1 "2022-04-26T20:05:31Z")

</div>

## Description of the feature request

Hey! When sending messages to Slack, you are able to specify a `thread_ts` parameter that matches the `ts` of a previously sent message in order to send the new message as a reply in a thread. Additionally, you can also specify `reply_broadcast` (boolean) to optionally send the message to the channel as well as in the thread.

For the reasons detailed in the Use Case below, it would be great for the Slack step to support this.

API documentation here: [chat.postMessage method | Slack Developer Docs](https://api.slack.com/methods/chat.postMessage)

## Use case / for what or how I would use it

We have a Slack bot that operates outside of Bitrise used to trigger builds from the Slack interface, when our builds run, the workflows often send at least a couple of Slack messages (one about the build starting, another about the result with links to artefacts etc) but this can mean that our deploy channel often gets noisy.

To help reduce noise in the main channel, it would be great if Bitrise could send the followup messages in the thread from the original trigger message. In addition, since failures are also important. It would be good if errors could be broadcast back to the original channel.

Because we first send an initial Slack message in an outside tool, we already have the `ts` of the original message, which is great but others might not have this value, so it might also be worthwhile for the step to return the origin messages `ts` value as an output so that it can be passed into subsequent step calls.

---

<div class="post-metadata">

**Author:** ![liam-nichols](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/liam-nichols/32/4362_2.png) [@liam-nichols](https://discuss.bitrise.io/u/liam-nichols)\
**Post date:** [April 26, 2022, 8:18pm UTC](https://discuss.bitrise.io/t/send-slack-messages-into-threaded-replies/19940/2 "2022-04-26T20:18:13Z")

</div>

Sorry I jumped the gun and submitted my patches as a PR anyway 😄 [Support sending messages into thread by liamnichols · Pull Request #80 · bitrise-steplib/steps-slack-message · GitHub](https://github.com/bitrise-steplib/steps-slack-message/pull/80) Feel free to close if you aren’t accepting community contributions still