TSB widgets can sit inside a Notion page, but “live” needs a precise definition. The widget is rendered from its current source when the embed loads; it is not a guaranteed streaming feed. Public market widgets use a URL with a widget ID. Account-data widgets use a separate revocable bearer token and show a read-only projection of the connected TSB workspace.
The safe setup is: choose the exact widget in TSB, copy the generated URL, embed it with Notion’s /embed block, test it in every client that matters, and treat a tokenized URL as a secret.
/widgets/widget?id=WIDGET_ID for a public widget and the URL generated by TSB for an account-data widget. A tokenized URL is read-only, but anyone who can obtain it may be able to view that projection. Rotate the link after accidental disclosure.
Why Add Current Trading Data to Notion
Notion is useful for plans, notes, databases, and review prompts. A TSB embed can place a market tool or account-data view beside that written context without copying a screenshot. The embed does not replace the underlying record: your source export, reconciliation totals, rule snapshot, and TSB journal remain the evidence layer.
Use an embed when it helps a defined decision. A public economic calendar can support morning preparation. A daily summary can support an end-of-day review. A performance chart can provide context while you work through a repeatable trade-review process. Adding widgets without a review question only makes the page heavier.
Step by Step: Embed Your First TSB Widget
- Open the TSB widget catalog. Sign in and go to Notion Widgets. The catalog prepares previews and copyable links after a usable Notion connection exists.
- Choose the access class. Public widgets contain market tools and need no token. Account-data widgets require a connected Notion workspace, an allowed entitlement, and TSB’s dedicated embed token.
- Copy the generated URL. Do not construct or shorten a tokenized URL by hand. Its widget ID is case-sensitive and uses hyphens.
- Open the target Notion page. Type
/embed, choose Embed, paste the HTTPS URL, and confirm the block. - Resize and test. Check the block at desktop and mobile widths, reload the page once, and verify that the displayed account and date range are the intended ones.
- Test as another viewer. Open the shared Notion page in the same permission state as its real audience. Do this before relying on the widget for a team or client workflow.
Notion’s official embed instructions support pasting an embeddable HTTPS link or using /embed; the block can be resized and placed in columns. Notion also warns that embeds which require login to an external site do not work in its desktop or mobile apps. TSB’s tokenized widget route avoids an external login prompt by carrying a read-only bearer credential in the URL, which creates the sharing tradeoff explained below.
Public and Tokenized URL Contract
Public widget: use the base https://app.traderssecondbrain.com/widgets/widget with one query value, id=position-calculator. The viewer receives a public market tool and no personal journal projection.
Account-data widget: the generated link uses the same base with both token=PUBLIC_EMBED_TOKEN and id=daily-summary. The viewer receives a read-only projection resolved from the connected TSB workspace. Remove page access and regenerate the embed link in TSB Settings to revoke it.
The dedicated embed credential is limited to public dashboard and public widget reads. It is not accepted as a private account login and does not authorize journal mutations, sync actions, private AI Coach access, or AI history. That scope reduces impact; it does not make the URL harmless. Possession of the bearer link is the viewing credential.
All 24 Embeddable Widgets in the Current Catalog
The server catalog contains 24 standalone widgets as checked on September 9, 2026. The groups below describe the current router rules, not a permanent feature or plan promise. The catalog and entitlement checks remain controlling.
Public Market Widgets — No Token
| Widget | ID | Default frame | Configured purpose |
|---|---|---|---|
| Position Calculator | position-calculator | 420×510 | Position sizing for supported market inputs |
| News Wall | news-wall | 800×400 | Trading-news feed |
| Market Pulse | market-pulse | 900×480 | Market-sentiment gauges |
| Chart Terminal | chart-terminal | 800×460 | TradingView chart and symbol selector |
| Forex Cross Rates | forex-rates | 800×550 | Currency cross-rate matrix |
| Market Overview | market-overview | 800×500 | Indices, forex, and crypto overview |
| Trading Terminal | trading-terminal | 800×220 | UTC clock, sessions, and ticker feed |
| Economic Calendar | economic-calendar | 800×450 | Economic events and importance filter |
Starter Account-Data Widgets — Token Required
| Widget | ID | Default frame | Configured purpose |
|---|---|---|---|
| Daily Summary | daily-summary | 450×180 | Current daily trading summary |
| What If Simulator | what-if-simulator | 420×380 | Counterfactual review of tagged trades |
Notion Chart Pack — Token and Eligible Access Required
| Widget | ID | Default frame | Configured purpose |
|---|---|---|---|
| Notion Charts | notion-charts | 960×430 | Wide analytical charts |
| Notion Donuts | notion-donuts | 360×360 | Compact summary donuts |
Advanced Account-Data Widgets — Token and Full Access Required
| Widget | ID | Default frame | Configured purpose |
|---|---|---|---|
| Quick Stats | quick-stats | 350×210 | Month-to-date summary metrics |
| Mini Equity Chart | equity-mini | 440×300 | Daily P&L bars |
| AI Insights | ai-insights | 440×320 | Generated trading observations |
| Profit Streak | streak-counter | 380×410 | Consecutive profitable-day history |
| Execution Protocol | execution-protocol | 450×650 | Pre-trade checklist |
| Weekly Summary | week-summary | 500×180 | Current weekly summary |
| Performance Radar | radar-mini | 430×400 | Behavioral-analysis dimensions |
| Morning Briefing | morning-briefing | 440×420 | Sessions, sentiment, and events overview |
| Monthly Comparison | monthly-comparison | 440×500 | Current month against prior month |
| Goal Progress | goal-progress | 440×220 | Monthly goal progress |
| Weekly Progress | weekly-progress | 440×420 | Weekly goal progress and comparison |
| Market Sessions | market-sessions | 800×500 | Global market-session indicators |
The listed width and height are defaults from widgets/widgets.json, not guaranteed minimums. Start with the catalog size, then resize the Notion block and verify every label and control. A wide table or chart may remain awkward on a narrow phone.
What “Live Data” Means Here
An embed request renders from the widget’s current available source. The result can still depend on upstream market data, the connected workspace, account filters, entitlement state, caching, and when Notion reloads the iframe. This guide does not promise streaming updates, a fixed refresh interval, or complete source coverage.
When a value looks stale, compare it with the underlying TSB screen and the preserved source export. Reload the Notion page, confirm the intended account scope, and check the data timestamp before changing a trading decision. For historical analysis, reconcile the imported row count, quantity, gross result, fees, and net result using the import-format acceptance checks.
Account-Data Sharing and Privacy
A shared Notion page and a tokenized widget are two separate access surfaces. Notion page permissions control who can open the page. The bearer URL controls who can ask TSB for the read-only projection. Use both controls:
- Keep the Notion page private or shared only with named viewers.
- Do not expose the embed URL in public templates, page source, screenshots, or tickets.
- Use the widget catalog’s account-scope control when the page should show one account rather than all accounts.
- Regenerate the embed link after a viewer leaves, a page becomes public, or the URL may have leaked.
- After rotation, retest every intended embed; old tokenized URLs should no longer work.
“Read-only” describes authorization scope, not confidentiality. A viewer can still read, capture, or redistribute whatever the widget shows. If the audience should not see performance data, use a public market widget or written summary instead.
Build a Useful Notion Layout
Start with one review question and one widget. A daily review page might pair Daily Summary with written evidence. A weekly page might pair Weekly Summary with the journal’s reconciled records. A market-preparation page might use Economic Calendar and a written risk plan. The Notion dashboard guide covers database and layout choices; the Notion journal guide covers the underlying record.
Do not duplicate a metric merely because another card exists. If a Notion formula and a TSB widget disagree, stop and compare cohort, timezone, account scope, net-versus-gross basis, excluded rows, and rounding. The formula guide provides denominator and readiness tests.
Troubleshooting Common Embed Failures
| Symptom | Likely boundary | Check |
|---|---|---|
| Notion creates a bookmark instead of an embed | Wrong block type or unsupported URL response | Use /embed, paste the full HTTPS URL, and open the same URL directly in a browser. |
| Widget not found | Unknown or malformed ID | Copy the catalog URL again; IDs are lowercase and hyphenated. |
| Connect Notion gate | Missing, invalid, or unusable token connection | Open TSB Settings, verify the Notion connection, then recopy the generated link. |
| Full Access or chart-pack gate | The widget is valid but the resolved workspace lacks that entitlement | Choose an allowed public or starter widget, or verify the exact account entitlement in TSB. |
| Previously working link stops | Embed token was regenerated or connection state changed | Copy the current generated link and replace the old Notion block URL. |
| Wrong account or period | Scope, timezone, or cohort mismatch | Check widget scope and date context against the source record. |
| Data appears stale | Notion iframe, TSB cache, or upstream source has not refreshed | Reload, compare timestamps and source totals, and avoid assuming continuous streaming. |
| Controls or labels are clipped | The frame is too narrow or short | Return to the catalog dimensions, widen the block, and test the target device. |
Do not disable browser privacy protections as a default fix. The supported account-data route is the generated bearer URL, not a third-party-cookie session workaround. If an external platform refuses framing or rewrites the URL, compatibility is Not verified until tested in that platform.
Where TSB Fits
Ownership disclosure: Trader’s Second Brain is our product. Notion supplies the page, permissions, and embed block; TSB supplies the widget route, source projection, and revocable embed credential. The server-rendered comparison on this page uses the canonical Notion and TSB provider catalog, while this setup and security verdict stays fixed until editorial review.
TSB currently recognizes 330 structured source profiles through canonical runtime truth. That count does not promise that every file or field imports correctly. Preserve the original export and reconcile a representative batch before using any account-data widget as review evidence.
Methodology and Verification
This guide was fact-checked on September 9, 2026 against the local TSB widget catalog, widget router, embed-token endpoint, settings controls, and authorization/revocation tests. Notion behavior was checked against its official embed documentation and editing basics.
The previous guide’s 22-widget count, session-only privacy promise, login-prompt claim, cookie workarounds, fixed refresh behavior, hard widget-count advice, unsupported platform compatibility, and sub-minute setup promise were withdrawn. Production remains read-only until a separately authorized import after the required code deployment.
Final Verdict: Embed the View, Not the Trust Model
Use public widgets freely for non-personal market context. Use account-data widgets only when the Notion audience may legitimately see the displayed projection. Copy the generated URL, preserve page permissions, test the exact client, and rotate the token when sharing boundaries change.
The embed makes current context convenient; it does not certify data completeness, replace reconciliation, or guarantee continuous updates. Keep the source record auditable and let the widget support a defined review decision.
