Menzzo Chatbot Backend

Purpose

menzzo-chatbot-backend is the Laravel backend behind chatbot business workflows. It serves APIs used by the chatbot UI and support automation around orders, SAV, refunds, coupons, and customer context.

Some local workspaces may still have this backend checked out under the older menzzo-chatbot-wrapper folder name. Keep repository docs and submodule references aligned with axelites/menzzo-chatbot-backend.

Stack

• Laravel 12 and PHP 8.4-era backend.
• Sanctum, Horizon, Livewire/Volt, and Vite where configured.
• Queue-backed jobs and operational APIs.

Connected Projects

• Menzzo Chatbot UI consumes this backend.
• SAV and Logidav provide operational context for customer support flows.
• Magento/front-office systems provide order, coupon, refund, and product data.
• Chatbot logs collect diagnostic and analytics records from chatbot activity.

Local Docs Submodule

The backend mounts global docs at global-docs/. From the backend repository root, use:

git submodule update --init --recursive
cd global-docs
npm ci
npm start
npm run build

Product search

Product Search for Dify documents the standalone GET/POST contract introduced by merged backend PR #564, response/error branching and the Dify migration checklist. The page pins the source revision and keeps deployment and cutover unverified.

To Expand

• API route inventory.
• Queue and Horizon runbooks.
• Dify integration contract.
• CI and deployment notes.

Dependencies

The documented connections are the Chatbot UI, Logidav, Magento, and the logs API. Exact route behavior and which support branches call each backend service must be checked in the owning code references.

Setup

Application setup is not established by this page. Follow the owning repository's README and setup instructions, and request the approved local access or environment you need. The shared documentation submodule and docs-site commands are described in the repository map and local development guide; they do not start this application.

Flows

Chatbot to business API covers the source-mapped path once its audit packet is integrated. Support and refunds covers the broader case boundary.

Diagnosis

Keep a failing UI request, backend response, and downstream service result as separate checkpoints; do not infer that a Dify response proves an order/refund operation completed. A backend-specific API/queue incident guide is missing here.

Evidence and gaps

The page records a Laravel stack and a linked docs submodule. Route contracts, local runtime setup, environment-dependent integrations, retries, and operational runbooks are incomplete.

Next evidence to add: source commit and file references for the owned boundary, then repository-specific setup and the relevant operations procedure. See the documentation coverage matrix for the system-wide gap record.