Integrations

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Written for somebody deciding whether to buy, not for somebody configuring.

Requested-by counts are more honest than a logo with no status, and they prioritise the roadmap.

Beta and live are distinguished, so nobody buys on a promise.

How it works

1
Integrations are listed for somebody deciding, not somebody configuring.
2
Requested-by counts are recorded when customers ask, which prioritises the roadmap for free.
3
Beta and live are distinguished, so nobody buys on a promise.
4
The agent answers does it work with X from these rows.

Best for

Things chosen by eye — products, venues, people.

Not the right choice for

Long lists someone needs to scan quickly.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Integrationrequired	text	The product, named as customers would.
Categoryrequired	text	What kind of tool it is, so the page can be browsed.
What it doesrequired	text	The capability in a sentence, written for somebody deciding whether to buy.
Availabilityrequired	text	Live, Beta, or a request count. A logo with no status is a promise.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Describes integrations; the connecting is Api connectors.
Request counts depend on the agent capturing the ask, so they undercount.
No per-plan availability, so an enterprise-only integration needs saying in the description.
Nothing verifies that a Live integration still works.

Before it works

What you have to provide, if anything.

Nothing.
Record the requests from day one. The count is the argument for building the next one.

In practice

A product asked weekly whether it works with an accounting tool.

“Does it connect to Xero?”

What was said to the agent

What the agent built

An integrations page with live, beta and requested states, and a count on the requested ones.

What changed

Xero reached fourteen requests and was built next. The count was the argument, and it was already collected.

Better with

These do a different job on the same data. An agent can have all of them.

API connectorsLive

The agent reaches outside itself for data or actions, and a broken credential should be visible before a customer finds it.

FAQLive

Visitors ask the same handful of things — hours, delivery, pricing, whether you do X — and the answers should be identical on the page and in the chat.

RoadmapLive

You want to tell customers or a team where the product is heading without committing to dates you will have to correct.

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.