Webhooks

What it does

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

Webhooks fail quietly by design — the sender retries and gives up — so the failure count is the only place it surfaces.

Last response code per endpoint, which is usually enough to diagnose without logs.

Inbound and outbound in one place, because a missed event looks the same from either side.

How it works

1
Inbound and outbound callbacks are recorded together, because a missed event looks the same from either side.
2
Failures are counted per day rather than only logged, so a pattern is a number.
3
The last response code is kept, which usually diagnoses without opening logs.
4
A sender that retries and gives up leaves a count behind it.

Best for

Comparing many records across many fields.

Not the right choice for

A phone. A table is the first thing that stops working narrow.

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
Endpointrequired	text	The URL receiving or sending, in full.
Eventrequired	text	Which event it carries, since one endpoint often takes several.
Last coderequired	text	The most recent HTTP response, which is usually enough to diagnose.
Failed (24h)required	number	How many failed in a day. The only place a quiet failure surfaces.

What it does not do

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

No replay. A failed webhook is recorded, not resent.
No payload capture, so what was sent is not inspectable here.
Counts are per 24 hours, so a slow-burn failure over a week reads as low.
No signature verification status.

Before it works

What you have to provide, if anything.

Nothing beyond the endpoints existing.
Pair with Activity log, which is where the surrounding sequence lives.

In practice

A platform notifying a CRM when a lead is created.

“The CRM has not seen a lead in two days.”

What was said to the agent

What the agent built

A webhook row showing 502s and fourteen failures in 24 hours.

What changed

Leads had been going nowhere since a certificate change. Nothing had alerted, because the failures were on the receiving end.

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.

Activity logLive

Changes are made by several people or by automation, and after an incident you need to know the order of events.

AutomationsLive

Repetitive reactions are being done by hand, and the trigger is something the system already knows about.

Questions

What data does the Webhooks page use?

It reads webhook records the agent has collected. Outgoing event hooks. 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 table the wrong choice?

A phone. A table is the first thing that stops working narrow. It is best for: comparing many records across many fields.

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.