n8n service enquiry intake and routing

A customer quote form connected to an inactive n8n workflow with validation, persistent duplicate checks, human review, exception holds, and a local operator register.

View GitHub repository
Back to selected work

Routing controls and operator states.

FORM INTAKEStructured service request

Contact details, service, location, timing, project details, and consent enter through one n8n form.

ROUTINGFive explicit outcomes

Accepted, duplicate, invalid, human-review, and integration-exception records each move to a named state.

OPERATOR STATERegister and review gate

The local register retains each outcome while uncertain enquiries wait for a written human decision.

Workflow structure

The main inactive workflow contains the form trigger, validation, persistent Data Table lookups, a human-review wait state, and controlled preparation steps. A separate inactive QA workflow runs the five synthetic scenarios.

Routing outcomes

Accepted, duplicate, invalid, human-review, and integration-exception records are written to named terminal states in the local Service Enquiry Register.

Execution boundary

Both workflows remained inactive outside controlled runs in n8n 2.31.6. No external credentials, CRM writes, booking calls, acknowledgements, emails, or SMS actions were attached or performed.

Service enquiry workflow implementation.

The same intake, routing, review, and operator-state structure can be adapted around the systems a business already uses.

Start a project