API connectors

What it does

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

Shows whether credentials actually work, not whether they were once configured.

A connector that is configured and failing looks identical to a working one until something asks.

Last-call time per connector, so a silent failure has a visible age.

How it works

1
Connectors are listed with their live credential state rather than their configuration state.
2
The last call and its result are recorded, so a failure has an age.
3
A connector that is configured and failing looks identical to a working one until something asks — this is the something.
4
The purpose column means a failure reads as a consequence rather than a name.

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
Connectorrequired	text	The external service, named as its provider calls it.
Purposerequired	text	What it is used for, so a failure has a consequence attached.
Statusrequired	text	Connected, key expired, or not configured. Whether it actually works, not whether it was set up.
Last call	text	When it last ran and whether that succeeded. Gives a silent failure a visible age.

What it does not do

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

Status is as of the last call. A credential that expired since will still read Connected until something tries.
No automatic re-authentication or key rotation.
No alerting; it reports state, and somebody has to look.
Provider-specific error detail is not normalised.

Before it works

What you have to provide, if anything.

Needs the credentials to exist. This surfaces their state rather than managing them.
Pair with Status page if customers should see the consequence rather than the cause.

In practice

A platform depending on payments, email and address lookup.

“Why are addresses not autocompleting?”

What was said to the agent

What the agent built

A connector board showing Google Places with an expired key and a failure three days old.

What changed

It had been failing silently for three days. Nothing had errored visibly; the field just stopped helping.

Better with

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

IntegrationsLive

Compatibility with tools people already use is part of why they would choose you.

WebhooksLive

Other systems notify this one, or it notifies them, and a missed event has real consequences.

Status pageLive

Customers depend on the service being available and, when it is not, they need somewhere to look that is not your inbox.

Questions

What data does the API connectors page use?

It reads connector records the agent has collected. Connected live APIs. 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.