Glossary · Data plumbing
Outcome webhook
A callback that tells the form what happened to a submission — the direction webhooks in this category almost never run.
One of 25 entries in the Endpoint Forms glossary.
Definition
An HTTP callback in the inbound direction: your CRM, ops tool, or a manual action tells the form what a given submission turned out to be — accepted, disqualified, closed, and worth this much.
It is unusual only in its direction. Every form builder has outbound webhooks. Almost none accept anything back, so a submission is a fact that is true at the moment it is created and never updated again.
Why it matters
It is the smallest possible mechanism for closing the loop. It does not require a CRM integration, a data warehouse, or a project — one POST carrying a submission id and an outcome is enough to make everything downstream of it possible.
“Most builders just send a flat webhook, but for a real automation, you need the automation to be able to “search” and “update” the submissions too. Another missing link is internal action on the form itself, like setting status, priority etc.”
And the requirement that came out of the research more clearly than any feature request:
“For me, the paid feature is dependable integrations, not prettier form fields. If a form maps cleanly into an ERP or CRM, handles conditional logic without weird workarounds, and fails loudly when a sync breaks, that’s worth paying for.”
In practice
- Carry a submission id, an outcome, a value, a currency and a timestamp. Anything else is optional; the id is not.
- Make it idempotent. The same outcome delivered three times must not become three outcomes, and retries are how delivery actually works.
- Allow restatement. Deals reopen and get requalified; the final answer is the last one, not the first.
- Reconcile on a schedule. Webhooks are lost — a nightly sweep for submissions past their expected disposition window with no outcome is what turns a best-effort feed into a dataset.
- Fail loudly. A sync that breaks silently is the same failure as a dashboard that reports fine while the pipeline is empty.
The common mistake
Trusting delivery instead of reconciling.
Webhook integrations are built assuming delivery and then quietly stop. The endpoint changes, a certificate expires, a retry budget runs out — and because nothing was expecting a particular volume, nothing notices.
“platform integration can break without warning”
The result is a dataset with a hole in it whose shape correlates with when the integration was broken — which is the worst possible bias, because the missing outcomes are not missing at random.
Related terms
- VerdictOurs
- Our name for the outcome written back onto a submission: Won, Lost, Disqualified, or Awaiting verdict — plus a value.
- YieldOurs
- Our name for the quality-adjusted metric: Yield rate is the share of submissions that reached a good verdict; Yield value is revenue per hundred submissions.
- Time to disposition
- How long from submission until you know what the lead was worth — the number that decides whether outcome-based testing is possible for you at all.
- Hindsight split testsOurs
- Our name for split tests ranked on Yield rather than completion rate — where the winner cannot be known at submit time, so the test waits.
- Lead scoring
- Ranking leads by attributes and behaviour — usually by scoring what the submitter told you about themselves.