n8n Charles Schwab Bot Enhancement

I already have a working n8n flow that places simple trades, but I now need to roll out what I call “Opción B”: full state management, support for complex orders, and a reliable kill-switch. The integration must talk directly to the Charles Schwab API, so proven experience with that specific broker is essential.

What’s left to build
• State logic: every open position and pending order must be tracked continuously, with status updates saved to my PostgreSQL instance and pushed to Telegram in real time.
• Complex orders: the flow has to create, monitor, and — when required — cancel OCO (One Cancels Other) orders using Schwab’s REST endpoints.
• Kill switch: a single flag in n8n (manual boolean, plus an optional webhook) should immediately cancel every open order and stop new ones from being submitted until re-enabled.

Acceptance criteria
1. A single n8n workflow file (JSON) I can import that contains the new nodes, credentials placeholders, and clear notes.
2. Successful placement, modification, and cancellation of an OCO order on a Schwab paper-trading account, demonstrated via screen share or recorded session.
3. Kill-switch toggling proves that no further orders are accepted while the flag is off.
4. State table in PostgreSQL shows live updates; Telegram receives the same events within 2 seconds.
5. Brief markdown README outlining environment variables, Schwab auth flow, and any rate-limit considerations.

Tech stack in play: n8n (latest), Node-based custom functions, PostgreSQL, Telegram Bot API, Charles Schwab REST.

If this aligns with your Schwab and n8n expertise, let’s schedule a quick call so I can hand over the current flow and credentials stubs.