> 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/formatting-messages.md).

# Formatting Messages

## General Formatting

Slack hasn't yet released an input block which includes the formatting options you're accustomed to, so for the time being, messages must be formatted using their special markup notation. The basics are are covered below.

{% hint style="info" %}
Check out [**Slack's help page**](https://slack.com/help/articles/202288908-Format-your-messages) for more examples.
{% endhint %}

* **Bold**

  Surround your text with asterisks.

  ```
  *abc*
  ```
* ***Italics***

  Surround your text with underscores.

  ```
   _abc_
  ```
* ~~**Strikethrough**~~

  Surround your text with tildes.

  ```
   ~abc~
  ```
* **Inline code**

  Surround your text with single sticks.

  ```
  `abc`
  ```
* **Code block**

  Surround your text with triple sticks.
* ````
  ```a
  b 
  c```
  ````
* **Blockquote**

  > Use a `>` character at the start of a new line.

  ```
  >abc
  ```
* **Bulleted Lists**

  * Begin each line with a dash and a space.

  ```
  - a
  - b
  - c
  ```

{% hint style="info" %}
For the time being, there is no way for Slack apps to produce actual bullets, meaning dashes will be rendered as dashes.

To produce a true bullet, you can paste this character into your message: `•`
{% endhint %}

* **Numbered Lists**

  * Begin each line with an number, a period, and a space.

  ```
  1. a
  2. b
  3. c
  ```
* **Links**

  Slack will make a it a clickable link if you paste the URL, but you can use a cobination of `<`, `|`, and `>` to format URLs.
* ```
  <https://happybara.io|happybara>
  ```

## Tag/mention a user in Nightowl messages (e.g. @dave) <a href="#mention" id="mention"></a>

#### There are ways to mention people and channels, though unfortunately the text inputs Slack provides don't allow for the same native experience you're used to.

Since Slack won’t prompt and complete the mention of a user or channel, so if you want to mention `@dave`, you will need to type it out in full.&#x20;

{% hint style="warning" %}
Mentioning users with **spaces** in their names will not work this way.
{% endhint %}

To mention a user with a space in their name, you will need to [**find their user ID**](<https://medium.com/@moshfeu/how-to-find-my-member-id-in-slack-workspace-d4bba942e38c >), e.g. `UA1A1A1A1` and format it as follows using the `<`, `@`, and `>` characters.

```
<@UA1A1A1A1>
```

{% hint style="info" %}
User IDs start with **`W`** instead of **`U`** in [**Enterprise Grid**](https://slack.com/enterprise) workspaces.
{% endhint %}

An easy way to check users are mentioned correctly is to send yourself a [**BCC**](/nightowl/reference/bcc-messages.md) message.&#x20;

We are looking forward to Slack eventually releasing text inputs that perform like the one you are used to, especially for emojis.

## Images/files in Nightowl messages <a href="#upload" id="upload"></a>

#### Unfortunately there isn't a clean way to attach files in Slack app modal flows yet.  For now though, if your image/file is hosted online (e.g. Google Drive) you can just provide the link to it.&#x20;

Another alternative is to upload the file in the  `File Browser` (located in the top left corner of your desktop Slack client window) and then click `Share`. After the modal pops up, instead of sending a message with your new file, you can click `Copy Link` and then use that URL in your message. When the message is posted, Slack will load or preview the file for the recipient.

##


---

# 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/formatting-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.