Inovus Email Worker

A Cloudflare Worker that handles contact-form submissions and inbound email for Inovus Labs.

For every incoming message — whether it arrives via POST /contact or as a real email — Workers AI drafts a contextual reply specific to the message. That draft is sent to the sender as the auto-reply body, and the same draft is included in the team triage email so a human can review or follow up.

No DB, no tickets, no Durable Objects. Stateless.

Architecture

flowchart TD
    %% ── Inputs ──────────────────────────────────
    F["Project Sites<br/>POST /contact"]:::form
    E["Inbound Email<br/>info@inovuslabs.org"]:::email

    %% ── Processing pipeline ─────────────────────
    W["Cloudflare Worker"]:::cf
    AI["Workers AI<br/>Llama 3.3 70B"]:::cf
    BUILD["Build MIME parts"]:::cf

    %% ── Outputs ─────────────────────────────────
    REPLY["✓ Auto-reply<br/>to sender"]:::reply
    TRIAGE["→ Triage email<br/>verified team inbox"]:::triage

    %% ── Flow ────────────────────────────────────
    F -->|JSON| W
    E -->|Email Routing| W
    W --> AI
    AI --> BUILD
    BUILD --> REPLY
    BUILD --> TRIAGE

    classDef form   fill:#FEF3C7,stroke:#F59E0B,color:#78350F;
    classDef email  fill:#FEF3C7,stroke:#F59E0B,color:#78350F;
    classDef cf     fill:#FFE4CC,stroke:#F38020,color:#7C2D12;
    classDef reply  fill:#DCFCE7,stroke:#22C55E,color:#15803D;
    classDef triage fill:#E0E7FF,stroke:#6366F1,color:#312E81;

Loading

Triage is delivered to TEAM_INBOX (a verified Email Routing destination you configure). The auto-reply goes to the sender via env.SEND.send(reply) on /contact, or message.reply() for inbound email. See Limitations.

Workers AI

src/process.ts calls @cf/meta/llama-3.3-70b-instruct-fp8-fast with a JSON-schema response_format:

{ "reply": "<3–5 short sentences, plain text>" }

The system prompt forbids inventing facts/links/timelines and tells the model not to sign off (the template handles that). On failure: a generic "Thanks for reaching out — we've received your message…" fallback is used so an auto-reply still goes out.

Cloudflare setup (one-time)

1. Add inovuslabs.org to Cloudflare DNS.

2. Email → Email Routing → Enable on inovuslabs.org (Cloudflare adds MX + SPF + DKIM).

3. Destination addresses → Add the address you will use as TEAM_INBOX and complete verification. That unlocks env.SEND.send() to your team.

4. Routing rules → info@inovuslabs.org → Send to Worker → support-email-worker.

5. Turnstile secret:

   bunx wrangler secret put TURNSTILE_SECRET

6. Deploy:

   bun run deploy

Environment variables

Var	Purpose
MAIL_FROM	From address for outbound mail (must be on a domain with Email Routing enabled).
TEAM_INBOX	Destination for the triage email. Must be a verified Email Routing destination.
TURNSTILE_ENABLED	"true" to require a Turnstile token on /contact.
TURNSTILE_SECRET	Set via bunx wrangler secret put.

Local development

bun install
bun run cf-typegen
bun run typecheck
bun run dev

Contact endpoint:

curl -X POST http://127.0.0.1:8787/contact \
  -H 'content-type: application/json' \
  -d '{
    "projectSlug": "spectrum",
    "name": "Jane Doe",
    "fromEmail": "jane@example.com",
    "subject": "Question about Spectrum",
    "message": "Hi, how do I run the demo locally?"
  }'

For Turnstile in local dev, set TURNSTILE_SECRET to Cloudflare's always-pass test key 1x0000000000000000000000000000000AA.

Inbound email simulation:

bunx wrangler email send \
  --from someone@example.com \
  --to info@inovuslabs.org \
  --subject "Test" \
  --body "Hello, this is a test."

Contact form contract

POST https://support-email-worker.<subdomain>.workers.dev/contact
Content-Type: application/json

{
  "projectSlug": "spectrum",
  "name": "Jane Doe",
  "fromEmail": "jane@example.com",
  "subject": "Question about Spectrum",
  "message": "...",
  "turnstileToken": "<token from cf-turnstile widget, if TURNSTILE_ENABLED>"
}

Response:

{ "ok": true }

projectSlug is ^[a-z0-9](?:[a-z0-9-]{0,30}[a-z0-9])?$.

File layout

src/
  index.ts             fetch + email entry points
  routes.ts            Hono app: POST /contact, GET /health
  process.ts           classify + build reply/triage MIMEs
  classify.ts          Workers AI call (json_schema response)
  utils.ts             turnstile, intent meta, html-strip
  types.ts             Env, Intent, Classification
  templates/
    shell.ts           shared HTML shell + escapeHtml
    auto-reply.ts      buildAutoReply (text + HTML)
    triage.ts          buildTriageEmail (text + HTML)
wrangler.jsonc         bindings: AI, SEND

Limitations

• TEAM_INBOX must be a verified Email Routing destination. MAIL_FROM must be on a domain with Email Routing enabled. Cloudflare may restrict who you can send to; see current Email Routing Workers docs.

Deferred

• Per-project FAQ / RAG before reply.
• Slack / Discord notifications on certain intents.