Automations

Rules from a recipe or your own, read back as one sentence, observed before they are armed.

Rules you would otherwise keep by habit, written down once: move the stop to entry when a trade has earned one R, get flat before the Daily reset, be told when half the day's Buffer is gone. Each one is designed, watched and armed on the Automations page, and nowhere else.

Starting a rule

Start from a recipe or from a blank rule. A rule is one of two families: Manage a position, which looks at each position on its own and acts once per position, or Guard the account, which looks at the clock, the Daily reset or the Buffer. The family decides what the rule can be made of, so a combination nothing could mean cannot be built.

The form reads back as one sentence above it, such as On FTMO ••42, when a position I opened gains +1.0 R, move its stop to entry, covering costs, once per position. Every underlined phrase leads to its field. A field that does not read yet turns its words red, and the editor counts what is left to fix before the rule can run. Every action is labelled by what it does to the account: Alert only, Moves a stop, Closes positions or Closes everything on the account. On a phone the same editor is six steps - account, family, when, only if, then, review - with the sentence kept on top of each.

Recipes you can arm today: Entry at +1R; Take half at +1R, entry the rest; Protect a naked position; Time stop; Flat 15 min before the Daily reset; Flat 30 min before the weekend close; Buffer alarm at 50%; Morning reminder.

Dry run, right now

Beside the editor, and behind each card's Dry run, the rule says what it would do right now on each open position of its account: where the stop would go, how much it would close, how far a position still has to run, or what would hold it. It is asked through the same gate as your own orders, and nothing is sent.

Telling you

A rule can tell you, as what it does (when a position gains +1.0 R, tell me) or after it acts (and tell me), once the venue has taken the action or has not answered. Telling is always in the app, and by email or Telegram where the rule ticks them, inside your Delivery settings. Before you arm a rule the page says if a ticked channel cannot reach you. A rule that is refused tells you once an hour, in the venue's words, and one that pauses itself tells you at once.

Observe, then arm

A rule is saved as a draft or into Observe, and nothing ever starts armed. In Observe it is checked every half second against your real positions and writes down what it would have done, and nothing is sent. When the runs look right you press Arm, with your prop firm's rule on automated tools shown once and, where the firm does not plainly allow them, ticked. From then on it acts at your broker through the same gate as your own orders, and the Journal says via Automation with a Support reference; a rule that only tells you sends nothing to the venue, so no firm rule applies to it. Each card lists its runs by day, with what the venue answered. One press pauses a rule, an account or everything; Risk rules, the Lock and Auto-flatten keep working either way.

Who gets what

Every plan designs rules and runs them in Observe, which sends nothing. A reminder on a clock, told in the app, can be armed on every plan; any other rule that only tells you on Starter, Pro and Premium, and one that acts on your broker on Pro and Premium. Nothing about this depends on speed: the latency targets are the same on every plan.

In the terminal

A position that an armed rule is watching, or that one acted on, carries a small mark on its row in the blotter, linked to Automations. It is a description, never a control, and nothing about automations is drawn on the chart: configuration and activity live on the Automations page only.

For orders from a strategy, use Signals: a TradingView alert arriving at your own endpoint, sized and gated exactly like a manual order.