> For the complete documentation index, see [llms.txt](https://happybara.gitbook.io/nightowl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://happybara.gitbook.io/nightowl/reference/draft-messages.md).

# Draft Messages

### Draft messages allow you to save a message to any number of conversations.

{% hint style="info" %}
**Conversations** include:

* Direct messages with other users
* Multi-person direct messages (group messages)
* Private channels
* Public channels
  {% endhint %}

### To create a draft message:

* Head to the **Nightowl** app home – make sure you are on the `Home` tab.
* Navigate to the `Draft Messages` section and click :page\_with\_curl:`New` button.
* Enter one or more conversations to BCC.

  > When more than one conversation is selected, **semicolons** will be used as delimiters to display the recipients after the message is created.
  >
  > E.g. a message to **separately selected** DM recipients @Jack, @Jill, and @Jen will show as`BCC: @Jack; @Jill; @Jen` whereas selecting a **group** DM between you, @Jack, and @Jill in addition to a separately selected DM with @Jen will appear as `BCC: @Jack, @Jill; @Jen`.
* Compose your message.
* Optionally enable the insertion of recipient mentions.

  > The variable `{@}` will be replaced with a user tag in IMs and `@here` in other conversations.
* Select whether or not to show the recipient(s) that this message is from **Nightowl**.

  > Default selection can be modified in [**App Settings**](/nightowl/getting-started/app-settings.md)
* Select whether or not to show previews of linked content in messages containing URLs.

  > Default selection can be modified in [**App Settings**](/nightowl/getting-started/app-settings.md)
* Click `Save` to save the draft.

### After creating a draft message, it can be deleted, modified, saved as a recipient group, or used to create a message of any type.

* Click :bomb:`Delete` to remove the draft message.
* The following actions are available in the overflow (`...`) menu:
  * :pen\_fountain:`Edit`

    * Edit the conversations in the recipient group

  * :mailbox\_with\_mail:`Send now`
    *  Send the draft as [**BCC message**](/nightowl/reference/bcc-messages.md) and optionally delete the draft message

      > The recipient(s) and message body can be edited

  * :stopwatch:`Schedule message`
    *  Create a [**scheduled message**](/nightowl/reference/scheduled-messages.md) from the draft and optionally delete the draft message

      > The recipient(s) and message body can be edited

  * :gear:`Make recurring`
    *  Configure a [**recurring message**](/nightowl/reference/recurring-messages.md) from the draft and optionally delete the draft message

      > The recipient(s) and message body can be edited

  *  :page\_with\_curl:`Create group`
    *  Create a **recipient group** from the draft and optionally delete the draft message

      > The recipient(s) can be edited

{% hint style="info" %}
All Nightowl messages are sent from your user. 

Recipients will **not** be able to tell that you did not send the message.
{% endhint %}


---

# 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://happybara.gitbook.io/nightowl/reference/draft-messages.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.