Cards · reads integration
Integrations
Third-party links.
A grid of tiles, one per item, image first.

Seasonal tasting menu

Canapé selection

Service — per waiter

Glassware hire
How it works
- 1
Each item contributes a title, a short line and an image if it has one.
- 2
Tiles reflow to the width available.
- 3
Selecting one opens the full record.
Best for
Things chosen by eye — products, venues, people.
Not the right choice for
Long lists someone needs to scan quickly.
Questions
What data does the Integrations page use?
It reads integration records the agent has collected. Third-party links. 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 cards the wrong choice?
Long lists someone needs to scan quickly. It is best for: things chosen by eye — products, venues, people.
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.
09:00
Team briefing
Atelier Nord
11:30
Guests arrive
60 covers
13:00
Service begins
Main hall
16:30
Breakdown
Crew of 4
Activity log
What the agent did.
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