Operational showcaseKilwhiss Online × Kilwhiss Automate

Real website journeys connected to working automation

This showcase explains how Kilwhiss website activity moves through controlled n8n workflows. It focuses on the customer journey, safeguards and business outcome—not private endpoints, credentials or customer data.

3connected workflows
Validatedbefore data moves
Trackedthrough persistent records
Human-ledwhen automation should stop
Live workflow portfolio

Three stages of a connected customer journey

These are active Kilwhiss operational workflows. The diagrams show their defined behaviour while keeping the production implementation private.

Live

Website quote handling

A visitor submits the Kilwhiss Online quote form. The request is checked for required details and consent, assigned a reference, classified for internal review and acknowledged to the customer.

WordPress formSecure webhookValidationEmail routing
01 · InputWebsite quote formProject, contact and consent details
02 · ControlValidate and classifyReject incomplete requests safely
03 · InternalRoute for reviewReference and project summary
04 · CustomerSend acknowledgementClear next step and response expectation
Live

Approved-client onboarding

An internal approval starts onboarding through an authenticated endpoint. The workflow validates the instruction, creates a durable onboarding reference, records the project and sends the appropriate client and internal messages.

Header authenticationApproval gateData TableDual notification
01 · ApprovalAuthorised requestExact approval phrase and required fields
02 · RegisterCreate onboarding recordPersistent ID, owner and checklist
03 · WelcomeContact the clientReference and onboarding expectations
04 · CoordinateNotify KilwhissStructured internal next action
Live

Controlled onboarding reminders

A scheduled workflow reviews projects still waiting for information. Only due records are selected. Each message is logged, reminders are capped at three and the final stage is handed back to a person for review.

Daily scheduleDue-date logicThree-message capHuman escalation
01 · CheckRead awaiting recordsDaily at 09:00 Europe/London
02 · DecideSelect due remindersAge, next date and reminder count
03 · RecordSend and updateTimestamp, count and next action
04 · EscalateReturn to a personAutomation stops after reminder three
No public credentialsSecrets stay within controlled workflow credentials.
No endless chasingReminder limits prevent uncontrolled messaging.
Visible ownershipRecords retain status, owner and next action.

What “live” means: all three examples are active Kilwhiss production workflows. This page explains their controlled behaviour without exposing public triggers, credentials, customer information or private execution data.

Could your website remove the same kind of friction?

We can map the customer action, internal hand-offs, safeguards and useful outcome before proposing a separately scoped automation.

Discuss a Connected Website