Form or event
HubSpot, GoHighLevel, scheduler, referral, or signed webhook.
How it works
From inbound submission to routed decision—in one traceable run.
The workflow sits behind your existing acquisition surfaces. It validates the payload, assembles context, applies qualification policy, writes the result, and logs the route.
01 / INGEST
Receive a trusted event
A form, scheduler, CRM, or webhook sends the lead payload. Required fields, signature, source, and payload shape are validated before processing.
ControlSchema validation + idempotency key
02 / ENRICH
Assemble approved context
The workflow retrieves only the CRM, campaign, firmographic, and engagement fields approved for the qualification use case.
ControlField allowlist + source trace
03 / DECIDE
Apply rules and bounded reasoning
Deterministic exclusions run first. The LLM evaluates contextual evidence against a structured rubric and returns constrained JSON.
ControlSchema-constrained model output
04 / WRITE
Update the CRM record
Score, tier, reasons, confidence, open questions, and a readable qualification note are written to mapped properties.
ControlField-level write map + audit data
05 / ROUTE
Execute the next approved action
n8n creates the task, sends the notification, moves the lifecycle stage, starts nurture, or opens a human-review item.
ControlExplicit branch + retry policy
Reference architecture
Small components. Clear responsibilities.
Each system does the job it is best suited to do. The CRM owns the record. n8n owns orchestration. The model interprets bounded context.
n8n context pack
Validates the payload, deduplicates the event, and retrieves allowlisted context.
Rules + approved LLM
Applies hard exclusions first, then evaluates evidence against a structured rubric.
Confidence gate
Routes low-confidence, strategic, or policy-sensitive decisions to human review.
CRM + next action
Writes score, reasons, note, owner, stage, and an auditable routing status.
CRM remains system of recordNo secrets in model contextHuman review available
Failure behavior
A workflow should fail visibly, not improvise.
Every external call can fail. Arcqual defines what happens when data is missing, a provider is unavailable, or the model returns an invalid response.
Invalid or incomplete payload
Stop qualification, preserve the source event, and send the record to a named review path.
CRM or provider timeout
Retry with bounded backoff. If the service remains unavailable, alert the workflow owner without duplicating the lead.
Low-confidence decision
Write the evidence and proposed outcome, but do not execute an irreversible route until a person approves it.
Operating model
What your team can inspect after every run.
| Record | Why it matters | Typical location |
|---|---|---|
| Source payload ID | Connects the decision back to the original intake event | Workflow execution + CRM |
| Qualification policy version | Shows which thresholds and rubric produced the outcome | CRM property |
| Input source list | Explains which approved evidence was used | Execution log |
| Score, reasons, confidence | Makes the decision reviewable by operators | CRM fields + note |
| Route and status | Confirms the downstream action completed or needs attention | n8n + CRM task |
Your architecture
See the exact components, data paths, and review gates for your stack.
We will map the workflow around your intake source, CRM objects, ownership rules, and approved model provider.