search

Step 5 – How to edit your bot and teach it new strategies

Editing a live algo-bot is mainly about “pause → clone → tweak → re-deploy”.

The exact menu labels differ from platform to platform, but the flow is always the same: freeze the bot so it can’t place new trades, duplicate or open its settings, inject the new logic (indicator, pair, risk rule, API payload, etc.), back-test the revision, then restart with fresh alerts / API keys. Below is a rapid checklist that maps those generic actions to the platforms we covered earlier, with links back to the lessons where each console was introduced in detail.

hashtag
1 Pause or Switch to “Edit” Mode

Platform
How to freeze the bot

3Commas

Click My Bots → … (three dots) → Stop – the bot finishes open deals, but won’t start new ones.

TradeSanta

My Bots → Pause. All future grid/DCA orders are suspended immediately.

WunderTrading

Bots → Signal Bots → Toggle OFF – stops reading TradingView web-hooks until re-enabled.

Make/Integromat

Open the Scenario, click the ON/OFF slider to “OFF”.

AutoView

Hover the Chrome extension, hit Disable to ignore alerts (same as d=1 flag).

hashtag
2 Duplicate or Open Settings

  1. Clone for safety – every platform except TradingView lets you copy the bot in one click (“Clone / Copy / Duplicate”). Why? You get version control and instant rollback if the new logic misbehaves.

  2. Open parameters – this is where you change pairs, indicators, order size, or attach a brand-new TradingView alert JSON.

hashtag
3 Inject a New Strategy

hashtag
3.1 TradingView side

  • Edit the script parameters (or choose a fresh public strategy via Indicators → Strategy).

  • Save, then Create Alert with the updated JSON payload you copied earlier (see “Test-Alert” lesson).

hashtag
3.2 Bot console side

  • 3Commas & TradeSanta – switch to the Strategy / Preset / Indicators tab and pick the new preset, or paste new TradingView web-hook text.

  • WunderTrading Signal Bot – click Edit → TradingView Alert and replace Enter Long / Enter Short templates.

  • Make – open the Scenario, plug the extra indicator field into the router, or add a new HTTP module that fires when action = "trail" for example. Save → “Run once” test.

  • Kryll / AutoView – drop a new block (Kryll) or update the alert syntax tokens (sl=, tp=, ts=) in AutoView.

hashtag
4 Back-test the Revision

  • Use the in-platform tester (3Commas, TradeSanta, Kryll) or TradingView’s Strategy Tester.

  • For Make + WunderTrading, fire a dummy alert from TradingView on a 1 min chart and inspect the Scenario Execution Log – no orders should hit the exchange until you re-enable.

Tip: keep a changelog in the bot notes panel; Make even stores previous Scenario versions automatically.

hashtag
5 Re-deploy

  1. Re-enable (toggle ON / Start) on every layer: Make scenario → WunderTrading bot → Exchange API.

  2. Watch the first live alert in the logs; verify the order hits the correct sub-account on Bybit.

  3. Calendar-remind yourself to rotate TradingView alerts every 60 days if you’re on a Pro plan.

By now, you already have a simple bot. Try to edit it right now to see how it works before you start the next lesson.

PreviousStep 4 – Launching your bot on the marketNextStep 6 – Monitoring and improving

Last updated