Which link should I use to embed an AirApp preview in an internal page?

Use iframeUrl as the iframe's src. The other Embed Link url is for opening the preview in a normal browser tab or an agent side panel: it exchanges the link token for a browser cookie and redirects. That redirected address is not the iframe address, especially when third-party cookies are blocked.

In the AirApp, open More actions (···) → Share → Embed. Choose an expiry and, for your internal page, set Where it may be embedded to Only these sites and enter your page's exact HTTPS origin (for example, https://intranet.example, without a path). Create the embed link and copy the iframe snippet shown there. The link and iframe URL are shown only when created, so keep the capability URL out of logs and public pages. A teammate viewing the internal page does not need a Busabase workspace login, but anyone with that active URL can read the content it exposes.

The default lifetime is 15 minutes; you can choose up to 24 hours. It stops working at expiry or immediately if you revoke it. That makes it a temporary preview, not a permanent link to hard-code into an internal page. For a recurring page, have an authorized server create a fresh link when needed and pass its iframeUrl to the page. Do not put a credential or link-minting call in the viewer's browser.

The AirApp runs its current merged files in the viewer's browser, but its embedded Busabase data access is read-only. Viewers cannot change workspace records through this embed, even if the AirApp UI has editing controls in its normal workspace view. The embed is not a frozen screenshot, so check what the app itself displays before sharing it; the target's visible content is not anonymized.

The Embed Links guide shows both URL formats, the iframe example, expiry, allowed-site policy, and revocation. Is this for a short review window or a page teammates need to keep open every day? That changes whether a temporary embed link fits your workflow.