Embed · reads embed
Embeds
External widgets/iframes.
Something from elsewhere, framed in place.
How it works
- 1
The external view loads in an isolated frame.
- 2
It keeps its own auth; nothing is proxied.
- 3
The surrounding page still knows which record it belongs to.
Best for
A tool the team already lives in.
Not the right choice for
Anything you could hold as data instead. Embeds cannot be searched.
Questions
What data does the Embeds page use?
It reads embed records the agent has collected. External widgets/iframes. Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a embed the wrong choice?
Anything you could hold as data instead. Embeds cannot be searched. It is best for: a tool the team already lives in.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Dev & automation

Seasonal tasting menu

Canapé selection

Service — per waiter

Glassware hire
API connectors
Connected live APIs.
Webhooks
Outgoing event hooks.
Datasets
Elastic uploaded data.

Seasonal tasting menu

Canapé selection

Service — per waiter

Glassware hire
Integrations
Third-party links.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free