> For the complete documentation index, see [llms.txt](https://docs.moonitor.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moonitor.tools/monitoring-commands/adding-quicktasks-buttons-to-pings.md).

# Adding QuickTasks buttons to Pings

![](/files/7U5088KpGwUXuAv2zmJ6)\
Adding QuickTasks is done by domain, QuickTasks are only available for site that show a SKU field on their pings.\
\
To add a QT you need to run the following command:<br>

```
$monitor addqt {domain} {qtname} {link}
```

In the link part put `moosku` where u want the sku to be present in the actual ping, for example for an Amazon ATC the command will be <br>

```
$monitor addqt amazon.com atc1 https://www.amazon.com/gp/aws/cart/add.html?ASIN.1=moosku&Quantity.1=1
```

You can have up to 5 QT per domain, they all will show on a ping. for example you can have\
&#x20;`ATC1 | ATC2 | QTWRATH | QTHAYHA`

## Show all QuickTasks

to show all QuickTasks type `$monitor showqt`

## Removing a QuickTask

To remove a QT you'll need the domain and the QuickTask link (u can view all QuickTask using `showqt`) \ <br>

```
$monitor removeqt {domain} {qtlink}
```

Example:<br>

```
$monitor removeqt amazon.com https://www.amazon.com/gp/aws/cart/add.html?ASIN.1=moosku&Quantity.1=1
```


---

# 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:

```
GET https://docs.moonitor.tools/monitoring-commands/adding-quicktasks-buttons-to-pings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
