SIGNALATOR
Autotrader Studio Tarifs Support
Signalator Notify · Setup

Set up Notify in a few clear steps.

Notify setup starts with access first: create an account, choose the plan you need, then connect the exact module path. If you want to see the product surface before attaching anything, open the shared demo workspace first.

Shared view-only demo Notify app downloads Android APK available
Open demo Create account Choose plan Downloads
Choose your Notify path Modules and help
Windows Monitor Trade Terminal Platform Health Trade Monitoring Price Watch
Health Trade Monitoring Price Watch FAQ
Setup logic

Create access first, then connect the module you want.

Notify setup does not start with an installer. It starts with account access. First create a free account. Then activate the Notify subscription you want. After that, move into Windows Monitor, Trade Terminal, or Price Watch setup.

Account · access · module From registration to first alert
1. Create a free account Start with a Signalator account so the workspace and modules have a real owner.
2. Get a subscription Activate the Notify access level you want before connecting live monitoring paths.
3. Choose what to monitor Windows Monitor, Trade Terminal, or Price Watch.
4. Connect the source Install, pair, or attach the correct sender path.
5. Select delivery Dashboard, mobile push, Telegram, and policy routing.
6. Confirm the first event Make sure the setup produces a visible alert.
Free account Subscription access Machine heartbeat Platform runtime Trade events Price levels Structured routing
Setup paths in practice

Three straightforward starting paths.

New users usually do not need a long manual. They need the shortest credible path from zero to the first working alert.

Windows Monitor path

For Windows PC, VPS, and server heartbeat monitoring

  1. Create a Windows Monitor source.
  2. Download or open the Windows monitor path.
  3. Pair it or save the configuration locally.
  4. Wait for the first online / recovered signal.
  5. Check offline / recovered delivery on the channels you selected.

Trade Terminal path

For trade events and optional platform runtime monitoring

  1. Create a Trade Terminal source.
  2. Choose the capabilities you want: Trade Monitoring, Platform Health, or both.
  3. Copy the sender token and attach the trading-platform path.
  4. Let the first trade event or platform heartbeat arrive.
  5. Check that the event appears with the expected privacy and delivery behavior.

Price Watch path

For level-based alerts without waiting for a trade event

  1. Create a Price Watch rule.
  2. Select symbol, comparator, target level, and repeat logic.
  3. Choose the channels that should receive the hit.
  4. Wait for the price rule to trigger.
  5. Use the hit as proof that your level-monitoring path is live.
What to switch on

Trade Terminal has two separate capabilities for a reason.

Inside Trade Terminal, Notify keeps trade activity and platform runtime separate. That makes setup more explicit now, and the alert stream much clearer later.

Trade Monitoring

Turn this on when you want position events, pending order lifecycle events, SL / TP updates, and profit or loss milestone monitoring.

  • Position opened, partially closed, closed
  • Pending created, modified, cancelled
  • Profit reached and loss reached milestone logic

Platform Health

Turn this on when you want runtime status for the trading platform itself. This is not a trade event feed.

  • Online, offline, and recovered platform reporting
  • Useful when one machine runs several terminals
  • Kept separate so runtime problems are not buried inside trade alerts
Delivery

Choose where you want to be told, then verify it.

Setup is not finished until the alert is visible where you expect it. Notify can surface events in the dashboard, send mobile push, and route to Telegram according to your policy structure.

Dashboard

Best for review, acknowledgement, and structured visibility across multiple monitored objects.

Mobile push

Best when you need immediate visibility without staying inside the web dashboard.

Telegram

Best when your workflow already uses Telegram and you want alerts routed there in parallel.

Policy logic

Best when different severities or event types should go to different places instead of everything going everywhere.

Need help?

Use Setup for the path. Use FAQ for clarification.

Setup should get you from zero to first alert. FAQ should answer the smaller questions around it, such as channel behavior, object differences, troubleshooting, and privacy detail.

Good first next step

Start with one object only. A single Windows Monitor, one Trade Terminal, or one Price Watch rule is enough to prove the path before you scale it wider.