# Trigger Types

Cortex supports several trigger types that can be used individually or combined as conditions for any order.

### Price Triggers

Executes an order when price crosses a threshold.

Supports standard instrument prices as well as [Pair Price triggers](#pair-price-triggers)

**Example:** start a HYPE limit chase when BTC > 100K USD.

### Candlestick Triggers

Execute an order based on candlestick OHLCV data. Supported intervals depend on the exchange:

1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 8h, 12h, 1d, 3d, 1w, 1M

### Candle Close

Executes when a candle **closes** above or below a price threshold. The condition is evaluated at the moment the candle closes.

**Example:** execute a BTC market order when the 4h candle closes > 75K USD.

### Candle Volume

Executes when a candle's volume crosses a threshold. Volume can be denominated in **USD** or **coin units**.

* **Volume > threshold:** can fire at any point during the candle as soon as volume is exceeded
* **Volume < threshold:** fires only at candle close, since volume can only be confirmed as "below" once the candle is complete

**Example:** execute when 1h candle volume > 100K USD.

### Time Triggers

Executes an order when time exceeds a specified threshold. Useful for scheduling entries, exits, or algorithm start times.

**Example:** start a TWAP at 8:00 PM UTC April 15, 2028.

### Pair Price Triggers

Supports synthetic pair prices derived from any two tokens on the same exchange. This allows you to trigger on price ratios even if the exchange does not natively list that pair.

Pair prices can be used with Price triggers.

**Example:** execute an order when ETH-USDC / BTC-USDC < 0.03.


---

# 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.insilicoterminal.com/documentation/cortex/trigger-types.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.