YKU
AI reads the inbox. A human keeps the send button.
Emails labelled AI-to-process are classified by the Kimi API inside a local n8n workflow that runs on the owner’s computer. The result is one internal summary — category, priority, and a proposed reply draft — delivered to the reviewer only.
No lead email is automatically sent. The only automated email is the internal summary to the reviewer.
Four steps, one human gate.
-
Gmail. Only emails tagged with the AI-to-process label enter the pipeline. Everything else stays untouched.
-
Local n8n. Your own machine polls the label, normalizes the message, and wraps it as untrusted data with injection protection.
-
Kimi classification. The Kimi API proposes a category, priority and reply draft as strict JSON. Invalid or suspicious output is forced into sensitive review.
-
Reviewer only. One summary email lands in the reviewer’s inbox. Replying to the lead stays a human decision, every time.
This page’s role is setup and status information only. It processes no email and holds no credentials.
Your setup checklist.
This checklist is editable and stored only in this browser’s local storage — nothing is uploaded anywhere.
Where things live.
The n8n link points to http://localhost:5678, which exists only on the owner’s computer. It cannot work for anyone else — that is intentional, not a bug.
A lead form on this page — later.
A future version may let visitors submit inquiries straight from this page. That requires n8n hosted at a secured public HTTPS address with an authenticated webhook, plus a deliberate opt-in. Until then the form below is disabled and cannot send any data anywhere.
Contact the team
Already Netlify-ready.
This site deploys straight from GitHub: netlify.toml already supplies the
build command (npm run build) and publish directory (dist).
- Sign into Netlify → Add new site → Import an existing project.
- Pick this site’s GitHub repository.
-
Confirm the build settings read from
netlify.toml— no changes needed. - Deploy. Every push to the main branch updates the site automatically.
Add no API keys or environment variables in Netlify — the static site needs none. Deploying this page does not make local n8n publicly accessible and does not connect Netlify to Gmail or Kimi. That is correct, and safer. Full steps live in docs/NETLIFY.md in the repository.