Email Notifications
Trade Automation Toolbox sends email notifications in the event of a number of actions or situations during the day. Some users filter or otherwise process these emails based on which notification it is.
Notifications will come from support@tradeautomationtoolbox.com.
Here is a list of possible email subjects you may receive:
Trade Opened ({account})
Trade Stopped ({account})
Trade Closed ({account})
Daily Profit Target Hit
Trade/Data Problem
Trade Activation Problem - Please check TWS
Scheduled Trade Entry Expired
Scheduled Trade Entry Aborted - Margin Issue
Unexpected Order Error - Margin Issue
URGENT: Missing Stop Detected
URGENT: Stop Monitoring Not Working
URGENT: Trade Over Fill Detected
URGENT: Trade Beyond Stop Detected
URGENT - High Slippage ({account})
URGENT: Unexpected TAT Processing Error
URGENT: Scheduled Trade Close Aborted
URGENT: Stop unable to be placed due to API precautions.
URGENT: Trade Quotes Missing or Outdated Detected
Webhook Notifications
Trade Automation Toolbox can also be configured to send notifications to a Webhook URL. Listed below are all of possible webhook notifications that might be sent and the example format for each message. Messages use simple html (<br> <b>) for message formatting.
Trade Opened
- Content Format:
- Starts with "Trade Opened<br>".
- Appends details for put trade (if present): "[Account] [Qty] [Strikes] [TradeType] @ [PriceOpen] [Strategy]<br>".
Appends details for call trade (if present): "[Account] [Qty] [Strikes] [TradeType] @ [PriceOpen] [Strategy]<br>".
Trade Stopped
- Content Format:
- "[Account] Trade Stopped<br>[Qty] [Strikes] [TradeType] [Strategy] <br> [StopType] Stop @ [PriceClose]<br>Trade Opened at: [PriceOpen] Slippage: [Slippage]<br>".
Trade High Slippage
- Content Format:
- "[Account] Trade Stopped with High Slippage<br>[Qty] [Strikes] [TradeType] [Strategy] <br> [StopType] Stop @ [PriceClose]<br>Trade Opened at: [PriceOpen] Slippage: [Slippage]<br><br><b>Order Details:</b><br><br><b>OrderID:</b> [BrokerOrderID]<br><br><b>Strike(s):</b> <br>" followed by leg details like "Qty: [Qty] Option: [Strike] [PutCall] Fill Price: [Price]" for each leg.
Daily Profit Target
- Content Format:
- "Daily Profit Target Hit<br><br>Please review your account positions to verify all trades closed properly.".
Trade Closed
- Content Format:
- "[Account] Trade Closed<br>[Qty] [Strikes] [TradeType] [Strategy] @ [PriceClose]<br>Trade Opened at: [PriceOpen] <br>".
Missing Stop
- Content Format:
- "URGENT: Missing Stop(s) Detected<br>[problems]<br>" (where [problems] is a string describing the issues).
Stop Monitoring Error
- Content Format:
- "URGENT: Stop Monitoring is not working as expected. We highly recommend restarting TAT and reconnecting to your brokerage. <br>[problems]<br>".
Webhook Test
- Content Format:
- "URGENT: Test Notification from Trade Automation Toolbox"
Trade Over Fill
- Content Format:
- "URGENT: Trade Over Fill Detected<br>[problems]<br>".
Trade Beyond Stop
- Content Format:
- "URGENT: Trade Beyond Stop Detected<br>[problems]<br>".
Outdated Data
- Content Format:
- "Trade/Data Problem Detected<br>[problems]<br>".
Api Pending Warning
- Content Format:
- "Trades Not Activating due to APIPending Status<br>This occurs when there is a problem with TWS. It is possible that stop order are not being placed properly. It is highly recommended to restart TWS and review orders to ensure all stops are in place. New opening orders will be disabled.".
Processing Error
- Content Format:
- "URGENT: TAT schedule processing is not working as expected. Please restart TAT and reconnect to your broker again.<br>".
Schedule Expired
- Content Format:
- "Scheduled Trade Entry Expired<br>[WindowStartTime] [ScheduleType] ([TemplateName]) did not complete successfully prior to the expiration time: [WindowEndTime] <br>".
Schedule Margin Error
- Content Format:
- "Scheduled Trade Entry Aborted - Margin Issue<br>[WindowStartTime] [ScheduleType] ([TemplateName]) did not complete successfully due to margin error. Account: [AcctNo] <br>".
Schedule Close Error
- Content Format:
- "URGENT: Scheduled Trade Close Aborted - Unknown Issue<br>[WindowStartTime] [ScheduleType] did not complete successfully due to an unknown error. Please review your account and take action, if necessary, to close this trade. <br>".
Other Margin Error
- Content Format:
- "Unexpected Order Error - Margin Issue<br>Unexpected order error due to margin error. <br> [msg]" (where [msg] is an error message).
Trade OCA Error
- Content Format:
- "URGENT: Your Stop Order was unable to be placed. <br> You need to change your API precaution (Bypass No Overfill Protection) setting immediately.<br><br> Please check the information at <a href='https://tradeautomationtoolbox.freshdesk.com/en/support/solutions/articles/151000039668-tws-order-precautions-preventing-orders-from-being-placed'>https://tradeautomationtoolbox.freshdesk.com/en/support/solutions/articles/151000039668-tws-order-precautions-preventing-orders-from-being-placed</a>".
Trade Quote Error
- Content Format:
- "Trade Quotes Missing or Outdated<br> {{Quote Errors}} <br> If quotes are not current, there may be problems processing early exit conditions and scheduled exits.<br><br> Please check the Quotes page in TAT and click the Refresh Quote Subscriptions button. If that doesn't help, restart TAT (and TWS for IBKR users) and reconnect.<br>.
Additional Notes
- Common Patterns: Many notifications prefix with "URGENT: " for critical issues. Dynamic data (e.g., [Qty], [Strikes]) comes from Trade, Settings, or other objects. Webhook bodies are often simpler than email bodies (no tables in webhooks, though emails sometimes include them).