Built by RESULTWARD
How RESULTWARD built its own lead intake pipeline
First-party engineering, built for this website. The enquiry form sends a validated brief to a server-side function, which forwards it to a vendor-neutral n8n workflow. Secrets never reach the browser.
Reviewed by RESULTWARD editorial.
Enquiry processing and delivery limits
Webhook acceptance does not prove that AI qualification, CRM delivery or notifications completed.
The browser sends eleven fields to a Cloudflare Pages Function.
The function validates the request and sends a normalized record to n8n using server-only shared-secret authentication.
The n8n workflow normalizes each enquiry and adds advisory qualification with a human-review fallback.
CRM and notification steps are configured separately by an operator.
Context and implemented scope
The website collects an outcome-first project brief. The browser sends eleven fields to a Cloudflare Pages Function. The function validates the request and sends a normalized record to n8n using server-only shared-secret authentication. This is first-party implementation evidence, not a client deployment or a measured business result.
Trust boundaries and delivery evidence
The endpoint checks same-origin requests, JSON content type, a bounded request body, email, objective and website protocol. Both webhook URL and shared secret are required. It accepts HTTPS webhook configuration, rejects redirects and uses a ten-second delivery timeout. A reference is acknowledged only after the webhook returns an accepted HTTP response.
How the behavior is verified
Contract tests exercise successful forwarding, missing configuration, malformed input, oversized bodies and downstream failures. Browser tests confirm that a failed delivery keeps the entries in the form and that a reference appears only after acceptance. The n8n workflow normalizes each enquiry and adds advisory qualification with a human-review fallback. CRM and notification steps are configured separately by an operator.
Known limits and next improvement
Webhook acceptance does not prove that AI qualification, CRM delivery or notifications completed. There is no durable queue or idempotency store in front of the webhook. A timeout after remote acceptance can lead to a duplicate on retry. Production verification must trace one reference through n8n and the configured destinations. Durable acceptance and destination reconciliation are explicit reliability improvements, not features claimed by the current implementation.
What the tests can and cannot show
The request contract and failure behavior can be reproduced without production credentials using mocked webhook responses. The form preserves user entries after failed delivery and shows no false success when configuration is missing. No claim is made about live conversion rates, time saved or production lead volume.