1
Feature request: interpolate record-context variables in IFRAME page-layout widget URLs (e.g. {{record.id}}, {{record.fieldName}})
Source: twentyhq/twenty#23145 · opened by @lineshFT
Use case We embed an external per-account analytics dashboard on Company record pages via the IFRAME page-layout widget. The external dashboard accepts the account as a URL parameter ( Today the widget URL is fully static, so every company record shows the same dashboard — the user must search for the account inside the embedded view on every record they open. What we verified (Twenty Cloud 2.x, July 2026 + current main) • Placeholder syntax in the widget URL (e.g. ?companyId={{record.companyId}}) is not interpolated — it is passed through literally to the iframe. On current main, the iframe widget configuration is just { url } (packages/twenty-server/src/engine/metadata-modules/page-layout-widget/dtos/iframe-configuration.dto.ts) and IframeWidget.tsx renders configuration.url unchanged via getSafeUrl, with no record context and no postMessage bridge to the embedded page. • Front components can't substitute for this: component-rendered iframes are force-sandboxed w…
No pledges yet. Be the first to back this.
Comments
Similar requests
App ecosystem: inline document preview inside record pages (DocumentViewer is modal-only)
1 vote · 0 comments
Dashboard visibility requires a separate, undocumented 'createDashboard' mutation not obvious from the page layout creation flow
1 vote · 0 comments
Reactive record updates in front components
1 vote · 0 comments
Attach an email to a person
3 votes · 0 comments
Support workflow variable binding for the Send Email action's Attachments field
1 vote · 0 comments
No comments yet.