> For the complete documentation index, see [llms.txt](https://threadly.gitbook.io/threadly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://threadly.gitbook.io/threadly/sending-messages/how-to-send-a-message-with-threadly.md).

# How to Send a Message with Threadly

Sending messages en-masse is a core functionality of Threadly. The flow is designed to be quick, simple, but powerful. Learn more below:

1. From the Threadly app in Slack, click "New Message" at the top right of the home screen of the app.
2. You'll now see the message editor. Here, you can craft your message:<br>

   <figure><img src="/files/c4JKFtnJWyVHoWzCzXFi" alt=""><figcaption><p>Click on the image to zoom in to view Threadly's message editor.</p></figcaption></figure>

   1. There are a few options available to you:
      1. To use a [template](/threadly/sending-messages/how-to-create-a-template.md), click "Add Template" to clone the template into your message.
      2. To attach an image, click "Add Image" and upload an image.
      3. To attach an Action, click "Add [Action](/threadly/actions/introduction-to-actions.md)" and select from your existing actions.
      4. To add [custom variables](/threadly/sending-messages/how-to-send-a-message-with-threadly/leveraging-message-variables.md) to your message, click "Message Variables."
      5. To customize [how the message is sent and its format](/threadly/sending-messages/how-to-send-a-message-with-threadly/message-settings.md), click "Message Settings."<br>

         <figure><img src="/files/qiw4ztrvv2Dk4uztVMTd" alt=""><figcaption></figcaption></figure>
3. Upon clicking next, you'll find the destination page. Here you can choose where your message should be sent. Depending on your plan, you will be limited to how many channels or DMs can be selected per each send.

   <figure><img src="/files/daqbuyemwI8tlmI87Ocz" alt=""><figcaption></figcaption></figure>

   1. **Channel(s):** Select from your channels
      1. Note: If you select channels, Threadly will check that it is a member of each channel and will offer a one-click solution to add Threadly if it is not a member. [Learn more.](/threadly/getting-started/adding-threadly-to-your-channels.md)
   2. **Conversation Group:** Select from your conversation groups, both dynamic and static
   3. **Direct Message(s):** Send a direct message to a user(s)<br>
4. If you're sending to a Channel or Conversation Group, you can also select the [token type](/threadly/faqs/how-threadly-sends-your-messages.md) (or how we send the message), and if you're using a "Bot" token, then [select the profile](/threadly/profiles/overview.md) that your message should come from.
5. The last screen is the preview screen. Here you can visualize how your message will look, save it as a template for future use, and when you're ready, hit send.

**Sending the same message frequently? Try** [**Workflows**](/threadly/workflows/introduction-to-workflows.md)**.**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://threadly.gitbook.io/threadly/sending-messages/how-to-send-a-message-with-threadly.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
