Build a Deriv bot without coding using blocks

You can build a Deriv bot without coding by dragging blocks into place in a visual builder, setting one condition for when a trade opens, and setting the limits that make it stop. No programming language, no syntax, no semicolons. This post walks through a simple bot from an empty screen, explains what each part does, and says plainly what it cannot do for you. Trading loses money for many people, and a bot does not change that.

A block based builder replaces the code you would otherwise write

In Bot Forge you work on a canvas. Blocks are shapes that snap together, and each shape holds one instruction: choose a market, choose a contract type, set a stake, check a condition, buy, wait, repeat. Connecting two blocks is the same act as writing a line of code, except the shapes only fit where the logic allows, so a whole class of mistakes becomes impossible to make.

The builder reads bot files from the older builders, so an XML file you already have from Binary Bot or DBot can be loaded and opened on the same canvas. That matters if you are starting from something rather than nothing, which is usually the faster way in.

Every bot is made of four parts

Almost any bot, however complicated it looks, is four things stacked together.

• Setup. Which market, which contract type, how long the contract runs, what the stake is. A Volatility index, rise and fall, a fixed stake.
• Purchase. The block that actually opens a trade. This is the one block that costs money.
• Condition. The rule that decides whether the purchase block runs on this pass or not.
• After the trade. What happens when the contract closes. Stop, repeat, or change the stake.

Build those in that order and the bot stays readable. Build them out of order and you end up with a canvas you cannot debug at eleven at night.

The condition is the only interesting part

The condition is where a bot stops being a repeat button and starts being a bot. It is a question the builder asks before it buys, and the answer is yes or no.

A condition can be as simple as checking the result of the last contract. It can compare the current tick to the previous one. On the digit contracts it can look at the last digit of the price and check whether it is over or under a number you choose. Whatever it is, it has to be something the builder can actually measure, because a bot cannot act on a feeling about the chart.

Start with one condition. A bot with one clear rule can be tested, because when it behaves oddly there is only one place to look. A bot with five conditions stacked on top of each other is a bot whose behaviour nobody understands, including the person who built it.

Limits are what turn a draft into something you can run

The limits are not an optional extra you add later. They are the part that decides how bad a bad session gets. Set them before the bot ever runs, not after.

A loss limit is the total amount you are willing to lose in a session, at which point the bot stops opening trades. A target is the same idea on the winning side: a figure at which the bot stops, because a bot with no target trades until the market takes it back. There is also the simplest limit of all, which is the number of trades. Ten trades and stop is a perfectly good rule for a first run.

Say those numbers out loud before you type them. If the loss limit is a figure that would ruin your week, it is the wrong figure, and the answer is a smaller stake rather than a braver limit.

A first bot, from an empty canvas

Here is the whole thing in order, with nothing clever in it.

1. Sign in with your Deriv account through Deriv's OAuth screen and switch to the demo account.
2. Open the builder and start a new bot, or load a free bot from the library and strip it back.
3. Set the market to a Volatility index and the contract type to rise and fall.
4. Set a small fixed stake. Small enough that the number does not distract you while you watch.
5. Add one condition. Something you can state in a single sentence.
6. Add the purchase block underneath it.
7. Set the loss limit, the target and the trade count.
8. Run it on demo and watch every trade it opens.

Watching is the step people skip. The first run is not there to make money, it is there to show you whether the bot does what you thought you told it to do. Those are different things more often than anyone expects.

What the builder cannot do

A bot executes a rule. It does not know whether the rule is any good, and it will follow a bad rule with perfect patience until the loss limit stops it. Building a bot without coding removes the technical barrier, and the technical barrier was never the hard part. The hard part is the condition, and that is still yours.

A bot also cannot touch your money beyond placing trades. The permission asked for when you sign in with Deriv is trading only. It reads the balance and places trades. It cannot withdraw and it cannot move money, and it never sees your password.

Where a free bot is faster than a blank page

Reading a working bot teaches you more than starting empty. The free bot library can be loaded, opened on the canvas and taken apart block by block, which shows you how somebody else answered the same questions. Change one block, run it on demo, and see what moved. The free bots and the library cost nothing to use. There are paid plans for the premium bots, and the pricing is on the site.

Open Bot Forge, load a free bot on a demo account, and change one block to see what it does.