# Webhook examples

We have a Long Correction 1H Screener signal inside Cryptovizor, designed specifically for intraday trading.

The signal logic is very straightforward:

`2h 🟡 AZT in Uptrend 🟢` - triggered only during a correction inside an uptrend, when:

MA50 is above the current price

MA200 is below the current price

`1h RSI14 Less than 32` - triggered during a deep correction, when the price has already pulled back significantly.

`1d USDT Volume Greater than 20M` - This filters out illiquid assets by daily trading volume to avoid slippage in both directions.

You can copy this signal and improve it by adding additional conditions - for example, distance to the nearest support zone, measured in percent.

After that, all that’s left is to automate the execution via webhook!

The Finandy configuration for receiving signals from Cryptovizor was covered in the previous chapter.\
Now we only need to prepare the actual webhook message that Cryptovizor will send to Finandy so orders can be executed on the exchange.

Below is a ready-to-use webhook example for trading:

### Webhook Example (Futures LONG with Key Levels)

{% code fullWidth="false" expandable="true" %}

```json
{
  "name": "DCU KeyLevels Futures LONG",
  "secret": "your_secret",                // Finandy generates this automatically — copy it from there

  "symbol": "{{ticker}}",                 // Ticker of the asset from the signal
  "side": "buy",                          // Open a LONG position

  "open": {
    "enabled": true,

    "scaled": {
      "price1": {
        "mode": "value",
        "value": "{{close}}"              // First order of the grid = current price
      },
      "price2": {
        "mode": "value",
        "value": "{{4h_support_center_price}}" // Last order = center of the 4h support zone
      },
      "qty": "5"                          // Number of orders in the grid
    },

    "leverage": "5",                      // 5x leverage
    "amount": "20",                       // 20% of account balance (with leverage)
    "amountType": "balanceLeverage",

    "schedulerMode": "day",
    "schedulerValue": "2",                // Auto-cancel unfilled orders after 2 days

    "timeoutMode": "pairLoss",
    "timeout": "1440"                     // Safety timeout: close the trade after 24h if the pair drops
  },

  "positionSide": "long",

  "tp": {
    "qty": 1,
    "orderType": "limit",
    "orders": [
      {
        "price": "{{1h_resistance_zone_low * 0.96}}",   // Take Profit: 4% below the 1h resistance zone low
        "piece": "100.0"                                // Close 100% of the position
      }
    ],
    "adjust": false
  },

  "slx": {
    "trailingBreakeven": "5",            // Move SL to break-even at +5% profit
    "breakevenSum": "200"                // Minimum position size required to activate BE
  },

  "sl": {
    "orderType": "stop-market",          // Stop-loss order type
    "price": "{{4h_support_zone_low * 0.97}}"   // SL = 3% below the 4h support zone low
  }
}

```

{% endcode %}

This is a complete webhook message that includes all essential parameters for the signal.\
The only additional recommendation is to define Order Density and Order Multiplier inside the Finandy signal settings (Open Position), because these parameters are not included in webhook messages by Finandy.

In the future, our platform will develop a collection of the best trading signals, and for each of them we will provide a ready-made webhook template.


---

# 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.cvizor.com/en/modules/signals/webhook/examples.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.