mojomaxi
Help / TradingView Webhooks Bot

TradingView Webhooks Bot

Connect TradingView alerts to a dedicated non-custodial strategy vault on Solana. When your set is running and a supported alert fires, Mojomaxi attempts the corresponding Jupiter-routed on-chain swap and records the result in Activity.

Video walkthrough with Seb Monty

Walkthrough of creating a set, funding a vault, wiring TradingView alerts, and monitoring automation.

docs

How the Webhooks Bot works

Core model

  • Each Webhooks set has a dedicated Token A / Token B configuration and its own vault.
  • BUY signals attempt Token B → Token A.
  • SELL signals attempt Token A → Token B.
  • Funds stay in the strategy vault. Mojomaxi does not move them into a centralized omnibus wallet.
  • The strategy must be in a running state before Mojomaxi will process incoming alerts for that set.

Setup steps

  1. Open /app and connect your wallet.
  2. Create a Webhooks strategy and choose Token A and Token B.
  3. Create the vault for that strategy set.
  4. Deposit Token B through the Mojomaxi dashboard.
  5. Copy the generated BUY and SELL webhook URLs shown in the app.
  6. Paste those URLs into the corresponding TradingView alerts.
  7. Click Start once the vault is funded and the alerts are configured.

Do not manually construct webhook endpoints. Always use the exact BUY and SELL URLs shown inside your Mojomaxi set so the set ID and execution direction are correct.

TradingView webhooks bot setup — create set, create vault, deposit Token B, connect alerts, start bot

TradingView alert tips

  • Use your normal TradingView condition logic and pair each direction with the correct Mojomaxi URL.
  • Name alerts clearly so it is obvious which one is BUY and which one is SELL.
  • The webhook endpoint itself determines direction. The alert message can stay simple.
  • Review your token pair carefully before starting. In this model, BUY means Token B → Token A and SELL means Token A → Token B.

What happens when an alert arrives

  • Mojomaxi resolves the target set and execution direction from the webhook URL.
  • The set must be running or the alert is ignored.
  • If signature or HMAC verification is configured, the request can be checked before execution proceeds.
  • Rate limits and per-set locks help reduce abuse and duplicate execution.
  • The executor checks the available input balance and attempts the swap through the same guarded backend machinery used elsewhere in the app.

Current requirements

A Webhooks strategy currently requires at least $50 of Token B in the vault before it can be started.

This minimum is a start requirement, not a guarantee that every later alert will execute. Route availability, slippage, token support, and remaining vault balance still matter after the strategy is running.

Why a signal may not execute

  • The strategy is not running.
  • The vault does not hold enough of the required input asset.
  • The request is malformed, duplicate, or blocked by a lock or rate limit.
  • Liquidity, route availability, slippage, or token constraints make execution unacceptable.
  • Infrastructure or network conditions temporarily prevent a clean execution path.

Important notes

  • Mojomaxi is non-custodial software and not investment advice.
  • Deposits should be made through the dashboard rather than by manually sending tokens to vault addresses.
  • Stopping the strategy should stop Mojomaxi from attempting future automated executions for that set.
  • Executed swaps appear in the Activity panel, while Metrics and share cards summarize strategy performance over time.
Need help with a specific Webhooks set? Open a Discord ticket with your wallet, set ID, and a concise description of the alert behavior you observed.