All commands in one list
Almost everything in Sync is done with buttons. There are few commands, and each has its own place: some work only in the private chat with the main bot, others in the chat with the notification bot, and a third group in the signal channel, for its owner only.
What it is
A command is a message that begins with a slash. The bot runs it right away, without walking through menus. A command with a typo, or one sent in the wrong chat, is not understood by the main bot, which answers “Unknown command”.
In the private chat with the main bot
The main bot is @sync_trading_bot.
| Command | What it does |
|---|---|
/start | Starts the bot, opens the main menu and the onboarding. The same command opens the bot from the links on the buttons under signal posts |
/export_history | Sends a CSV file with all closed trades |
/export_grid_history <id> | A CSV with the level history of one Grid bot; the id is the bot number from its card |
/export_dca_history <id> | A CSV with the cycle history of one DCA bot |
/export_all_history | One CSV with the whole history of all DCA and Grid bots; large files arrive in parts |
/set_kill_switch <percent> | Turns on the kill switch with a drawdown limit, for example /set_kill_switch 25 |
/disable_kill_switch | Turns the kill switch off |
/kill_switch_status | Shows the kill switch state: off, active or triggered |
All of this is also available through buttons: the kill switch is in the 🛡️ Kill switch section of the main menu (✏️ Change limit, 🔒 Disable kill switch, 🔄 Reset trigger), and trade history is in 💼 Trades → History. More on this: Exporting history to CSV, Kill switch.
In the chat with the notification bot
The notification bot is @Sync_trading_notifications_bot. It understands only two commands:
| Command | What it does |
|---|---|
/start | Connects the notification chat |
/stop | Disconnects the notification chat |
After /stop the bot writes: “Notifications disabled. You can re-enable them with /start.” To any other message it replies with a reminder: “Commands: /start — enable notifications, /stop — disable.” How to connect the notification bot is described in Notification bot.
In the signal channel (channel owner only)
These commands are typed right in the channel and act on the trades of all subscribers, so they are available only to the person who connected the channel to Sync. The /close and /change_… commands are sent as a reply to the signal post.
| Command | What it does |
|---|---|
/activate | Turn on processing of the channel's signals |
/deactivate | Turn off processing of the channel's signals |
/close (as a reply to the post) | Close the signal; subscribers' open positions are closed at market |
/close_all_signals | Close all active signals of the channel (no reply needed) |
/change_sl_to_<price> (as a reply) | A new stop-loss price |
/change_tp<N>_to_<price> (as a reply) | A new price for take-profit number N |
/change_entry<N>_to_<price> (as a reply) | A new price for entry number N |
What a subscriber sees for each command and how the bot confirms it is described in Commands in the channel.
Common mistakes and what the bot says
- “Unknown command” — a typo in the name, or the command was sent in the wrong chat.
- “Signal management commands must be sent as a REPLY to the signal post.” —
/closeand/change_…were sent as an ordinary message instead of a reply to the post. - “Could not parse the command. Examples: /change_sl_to_56780, /change_tp1_to_0.545, /change_entry2_to_56,4” — the price after
_to_could not be read. - “ℹ️ Usage:
/set_kill_switch <percent>. Example: /set_kill_switch 25. Allowed: 1.00 – 99.99” — the percentage is missing or out of range. - “❌ Grid bot with this ID was not found or belongs to another user.” — check the bot number on its card; for a DCA bot the text is the same.
- “ℹ️ You have no closed trades to export yet.” — there is nothing to export.
- “⚠️ Too many requests. Please wait 10 sec. and try again.” — the bot accepts no more than 30 requests per minute; this is not a block.