DoneAlgo setup guide

Webhook setup

TradingView requires two-factor authentication for webhooks. Copy the URL into Notifications → Webhook URL and the generated message into Message. Save the alert, trigger a test, and check Signal activity. Queued means waiting; Filled confirms a trade fill. Sent or Delivered describes a notification, not a trade.

Open Workflow and select its TradingView trigger to copy the private webhook URL and generated alert message. Each workflow URL addresses its connected destinations. Select the workflow and signal action before copying; the supplied Pine example can help with strategy alerts.

Use generated trade JSON or select Message only for text notifications without trades. Existing shared-webhook alerts continue to work; their message still needs the workflow ID and private token. Keep webhook URLs and private tokens secret, and never include exchange API credentials.

Tokens are generated automatically, encrypted on the server and loaded into your messages. Older hash-only tokens can be restored in Workflow by entering the existing token. Regenerating webhook credentials invalidates the previous token and all workflow URLs immediately. Pause TradingView alerts, regenerate, update every alert and then resume.

JSON & targets

The Pine example puts the workflow ID, pair, side and action inside strategy.order.alert_message. Replace its bot ID with the selected workflow’s ID. For a single entry, copy the generated JSON. Risk-sized entries require SL_TYPE and its matching stop_loss value; the default Pine example does not supply a stop loss.

For exits, keep the same workflow ID and pair, match the open position’s long or short side, and use close_all or exit_partial with a numeric percent. API requests need a current UTC timestamp and numeric price. TradingView placeholders such as ticker and close are resolved by TradingView. Notifications can use the selected action by default or your custom message.

One alert routes to all enabled destinations of the selected workflow. Each trading destination uses its own position size and exit settings. A linked bot uses its workflow’s shared alert ID; remove its workflow connections before deletion. Saved messages are available from the bot’s Messages menu.

Pips, points and entry exits

One point is one unit of the pair’s quote currency. Pips use each destination’s configured pip size: a pip size of 0.01 means 10 pips equals 0.10. Configure pip size before using pips. For long entries, absolute take profit must be above entry and stop loss below; shorts use the reverse.

TP/SL message values apply to that entry and change only the message you copy. Existing bot exit settings remain active. MT5 attaches targets as broker SL/TP levels. For exchange destinations, DoneAlgo monitors targets and submits market exits; these are not resting exchange orders, and actual fills can differ.

Automatic exits include take profit, stop loss, break-even and trailing stop. Percentages describe price movement before leverage and fees. Exit monitoring continues while the browser is closed and entries are paused, and depends on DoneAlgo’s server and exchange availability. New exit settings apply to new positions after saving.

Connections & plans

1 connection = 1 connected workflow destination. Each exchange, paper trading, MT5 or messaging destination counts separately. Using the same account in multiple workflows or markets uses a connection for each destination. Saved accounts that are not attached to a workflow do not count.

Saved MT5 accounts and messaging destinations can be reused without entering credentials again. Removing a workflow keeps its saved connections. When all plan slots are used, existing destinations stay active. Remove or disconnect a workflow destination, or upgrade before adding another. Each reuse in a workflow uses another plan connection.

Exchange funds remain in your exchange account. Demo uses test funds; Live uses real funds. Connect the selected market in Connections if your account is not listed. Verify each market from the connection’s menu. A public endpoint failure can prevent verification; changing the API key will not fix a server access problem. Troubleshooting timings measure connectivity only.

MT5 pairing

Add an MT5 connection and follow its pairing steps in your own terminal. Use the exact account and server, and check the required terminal settings before sending an alert. Demo and live accounts are distinct connections. MT5 orders and positions should also be checked in the terminal.

A disconnected MT5 account does not count toward your plan. Reconnect by pairing a new connection; previous trades remain in Signal activity. Disconnecting a connection or deleting a workflow does not close broker positions for you.

Sessions & security

Use at least eight characters for your password; a long, unique password is best. Enter the current password, then matching new and confirmation passwords. Contact support to change your email.

Sign out on all devices ends your sessions; existing access tokens may remain valid until expiry. You will need to sign in again. Close broker positions and pause bots before requesting account deletion. Deletion opens an email request for review; your account is not deleted until support confirms completion. Support reviews requests to avoid orphaning orders or positions.

Bot settings and execution

Name each strategy so you can identify it in positions and logs. All signal sources use DoneAlgo’s JSON format. Paper trades use simulated funds at the alert price; exchange trades use the exchange’s actual fill price. Spot supports long entries; futures supports long and short entries. COIN-M uses whole USD-value contracts, with margin and fees in the underlying coin.

Binance futures requires one-way mode, single-asset mode, isolated margin and leverage matching the bot. Delta requires isolated margin, automatic margin top-up disabled and matching leverage. Exchange minimum order sizes apply after quantity rounding.

Fixed notional sets trade value; coin quantity sets base-asset amount; percentage sizing uses available balance with a 1% fee buffer. Risk sizing derives quantity from the entry stop-loss distance, before fees and slippage. Each pyramiding entry adds its own risk budget. Maximum capital caps combined exposure and each new entry. Leverage changes required margin, not order notional or risk budget.

Pyramiding adds same-direction entries within capital and entry-count limits. Entry cooldown is the minimum time between accepted entries; zero disables the cooldown. Any pair reserves supported pairs for the account and market and requires a pair in each alert. Unavailable pairs show the bot using them.

Saving preserves a bot’s ID and paused status. Linked account, market and pair fields are locked until the workflow connections are removed. With an open position, only the pyramiding limit can be edited. Close exposure before changing other settings or deleting. Pending orders or unavailable exchange status temporarily lock editing. New live bots start paused and require activation and explicit real-money acknowledgement.

Workflow canvas

Click a node to configure it. Drag nodes to arrange them; drag blank space to move the view. Use Fit to show every connection, Ctrl + scroll or pinch to zoom, and Reset layout to restore the arrangement. You can also move a focused node handle with arrow keys.

Late or expired signals

Maximum age from the alert timestamp: Paper 120s · Exchange admission 120s · MT5 60s. Alerts can also expire while queued. These limits are fixed, not adjustable bot settings.

Use current UTC timestamps, check TradingView delivery times and investigate queue delays. Do not increase age limits just to hide an unexplained delay.

History availability

History is paginated in batches of 25. Paper trading keeps your last 500 entries. Other activity is kept for 90 days. Minimal duplicate-prevention and unresolved-order safety records may be retained longer.