# Signal list
**To create a rule and give an order to your bot, you need:**\
Step 1 - A signal reference/same name (ex: 'long', 'custom 1')\
Step 2 - Create a rule with the [Indicator Box](/strategy-boxes/indicators-box.md) that will trigger the signal if parameters are met\
Step 3 - Create a rule in others boxes that will execute a specific task once the same signal is triggered on Step 2.
You can create and manage your signals on the request Backtest Box. There are defaults signals, \[Long, Short, Stop, Cancel], that can't be deleted. \
You can create new custom signals, with the name you want, so you are free to use them on others boxes like classic signals, so you can customize your strategy as you wish.
Click on the '+' to create a new signal, choose a name and then you'll be free to use it on all others boxes. Refer to the [custom signal page](/how-it-works/signal-list/custom-signal.md) to learn more how to use it.
Signals creation box
**Every available signal can be triggered from any indicator.**
*Ex: \[RSI cross 80]\[Place a Long signal]*
*When the RSI hits 80 on the selected timeframe, a long signal will be triggered on your general strategy. However, it will only open a long if the conditions are met with others rules from the*[ *Entry in position rules Box*](/triggers-boxes/entry-in-position-rules.md)*.*
***Signal Rules**:*
A signal turns ON as soon as the trigger rules are met (typically at the candle close, though it can occur intra-candle depending on the trigger conditions).
By default, the signal turns OFF after one candle on the indicator’s timeframe.
When there is a single signal duration rule, it overrides this default behavior.
When there are two or more rules, the signal will turn OFF once all specified rules have been met."
---
# Agent Instructions: 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.runbot.io/how-it-works/signal-list.md?ask=
```
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.