Classify fictional support requests once. Persist the outcome and its audit together, with accountable human-review decisions.
n8n
JavaScript
MySQL
Docker
Ollama
Locally verifiedLive on Oracle CloudReal AI classification with Ollama
INTERACTIVE DEMO
Try the support-ticket automation.
Submit a fictional ticket to see real AI classification, saved status and audit history. Runs on Oracle Cloud.
Review pending tickets created in your demo session. Decisions appear in the saved audit timeline.
HISTORICAL TEST SNAPSHOTS
Testing & Reliability
Browse 13 historical snapshots. Each preserves the original execution date and recorded outcomes, including PASS and ERROR. These results describe past runs. Isolated, mocked, and infrastructure checks are labeled separately.
Local validation service must be available. Runs only isolated and mocked checks; no ticket or workflow actions.
Loading stored test evidence…
What I built
I connected n8n, JavaScript, MySQL and Ollama into a support-ticket pipeline with validated inputs, safe retries, transactional audits and authenticated human-review decisions. This demo submits synthetic tickets through the existing isolated automation.
Input → protected API → n8n → Ollama → MySQL result and audit.
THE BUSINESS PROBLEM
Support queues need consistent triage without duplicate processing, lost outcomes or unaudited manual decisions.
ARCHITECTURE / DATA FLOW
A clear path from input to outcome.
01
Validate
A protected backend bounds fictional input and assigns a synthetic ticket ID.
02
Claim & classify
n8n claims the ticket in MySQL before asking Ollama to classify a new request.
03
Persist & review
A transaction saves the result and audit; unusable AI output waits for authenticated human review.
ENGINEERING CHOICES
Where reliability needed deliberate design.
Retries must not become duplicate work
A payload fingerprint and conditional claim replay identical requests and reject changed content.
A result needs an audit
Ticket updates and audit insertion share a transaction; failure tests check rollback.
A demo must not reach unrelated data
A separate schema, restricted account, synthetic identifiers and private webhook isolate the demo.
TESTING / VERIFICATION
What the recorded tests established.
Previously recorded project results, not tests rerun by this website. Website CI checks the portfolio itself and does not execute these automations.
Selected actual test cases from each recorded suite. Outcomes below are previously reported PASS, not fresh automation runs or a complete case listing. Current source was inspected to identify the inputs and assertions; there is no public raw-results archive.
Backend checks
34 checks in the recorded suite · 2026-11-11
Actual local Node HTTP server; injected upstream fixtures. No n8n, MySQL or model execution.
Source: tests/demo-api.test.mjs in the automation repository. Public source excludes private runtime configuration and raw execution evidence.
Valid fictional ticket
Previously reported PASS
Test input
A unique requestId, fictional=true and “For a fictional order I was charged twice. Please investigate.”
Expected
Accept the request and return only safe result fields.
Recorded result
Response keys matched category, reason, status and ticketRef.
Returned exactly {httpStatus:503,errorCode:REVIEW_UNAVAILABLE}.
How checked
Deep equality of the entire returned object.
Why it matters
Keeps internal database details out of public responses.
Reviewer integration checks
20 checks in the recorded suite · 2026-11-08
Actual reviewer DEV webhook and MySQL with synthetic PENDING_REVIEW fixtures. Historical runs, not executed for this website change.
Source: tests/review-integration.test.mjs; docs/TESTING_GUIDE.md §3 in the automation repository. Public source excludes private runtime configuration and raw execution evidence.
Missing or wrong authentication
Previously reported PASS
Test input
APPROVE body with missing authentication, then intentionally invalid authentication.
Expected
403; ticket and terminal-audit count unchanged.
Recorded result
Recorded 403 for both; ticket remained PENDING_REVIEW, requires_review=1, UNKNOWN and zero terminal audits.
How checked
HTTP status assertions plus independent DB SELECT. Empty execution history alone is not proof of unchanged data.
Why it matters
Prevents unauthenticated ticket decisions.
Approval commits ticket and audit together
Previously reported PASS
Test input
Synthetic pending ticket, decisionId=decision-1, APPROVE, BILLING and a synthetic reason.
Expected
200; APPROVED, review flag cleared and one terminal audit.
Recorded result
Recorded 200/replayed=false; APPROVED,0,BILLING,1. Durable audit reference 11282.
How checked
DB SELECT and auditDetails checked fixed reviewer, previous/new status and matching reason.
Why it matters
Makes the accepted decision accountable and durable.
Identical decision is replayed
Previously reported PASS
Test input
Repeat exactly the committed approval.
Expected
200/replayed=true without a second terminal audit.
Recorded result
Recorded replay=true and exactly one terminal audit.
How checked
HTTP replay flag assertion and DB count.
Why it matters
Makes browser/network retries safe.
Two competing decisions
Previously reported PASS
Test input
Two simultaneous decisions for one pending ticket with different IDs/categories.
Expected
One 200 and one 409; exactly one terminal audit.
Recorded result
Recorded status set [200,409] with one terminal audit.
How checked
Promise.all; sorted status assertions; real DB count.
Why it matters
Ensures only one decision wins a race.
Audit insertion failure rolls back the ticket
Previously reported PASS
Test input
Synthetic pending fixture; historical test temporarily made the required audit event invalid with SQL NULL.
Expected
503; ticket remains pending with no terminal audit.
Recorded result
Recorded PENDING_REVIEW,1,UNKNOWN,0 after 503. Restored SQL then accepted the same decision with 200.
How checked
Independent SELECT after failure and recovery request. Final audit rows alone cannot reconstruct the transient rollback observation.
Why it matters
Prevents an approved ticket existing without its mandatory audit trail.
Reviewed tickets replay through intake
Previously reported PASS
Test input
Replay original synthetic ticket fields after APPROVED and REJECTED decisions.
Expected
200 with terminal status; no new classification or outcome write.
Recorded result
Recorded APPROVED and REJECTED replies; execution references 11297 and 11298.
How checked
Saved intake node data checked fields, no Classify Ticket/Save Ticket Outcome, and zero claim audit insertion.
Why it matters
Prevents a customer retry from reclassifying a completed human decision.
Source: Project README, root handoff and Milestone A testing guide. Local documentation reviewed 2026-11-12. Counts are separate suites, not a combined coverage score. Raw execution payloads and private receipts are excluded.