AlgoVesta › Glossary › Automation flow

Signal & Automation

Automation flow

An automation flow is the full path a trade takes without human action: a signal is received from its source, parsed into structured fields, checked against risk rules, sent to the exchange or broker, protected with stop-loss and take-profit orders, monitored while open, and recorded when it closes.

Why it matters

Every step in the flow is a place where a trade can silently fail: a message that is not parsed, a rule that blocks without telling anyone, an order that is rejected, a stop that is never confirmed. Understanding the flow tells you where to look when "the bot is not trading" and what a platform must show you at each stage. It also defines what running unattended really means: the steps after the entry, protection and monitoring, are the ones that matter most while you are asleep.

How AlgoVesta handles it

AlgoVesta's flow is the same for every source. A Telegram message, a TradingView webhook or an MCP request is received and parsed; the bot's preflight checks confirm that the account, permissions and required settings are in place before the bot is even allowed to start; each signal is checked against the bot's rules (size, leverage cap, stop requirement, open-position limits, daily loss, drawdown, cooldown); the order is sent to the venue and the fill is read back from the venue's confirmation; stop and take-profit orders are created on the venue and verified; open positions are watched for break-even, trailing and auto-close rules; and closed trades are reconciled against the venue's history. Every blocked or failed step is recorded with a reason visible on the bot card and in the dashboard, and a bot that blocks several signals in a day without executing triggers a summary email. The same flow runs in paper mode with a virtual balance. An overview is on the crypto automation page and the TradingView bot page.

Example

At 02:14 a channel posts "XAUUSD BUY 2410 SL 2402 TP 2425". The message is parsed at 02:14:00.1, passes the rules (the bot has two open positions of a maximum of four, no daily loss lock), the market order is sent to the MetaTrader 5 terminal and fills at 2410.35, the stop and target are set on the position and confirmed, and the position appears in the dashboard within seconds. At 05:40 the target is hit, the terminal closes the position, and the closed trade is synced with the broker's deal record.

Common mistakes

In practice

See how AlgoVesta automates this