Store contact submissions in a KV namespace

Bind a SUBMISSIONS KV namespace and persist every valid submission as a
durable record (keyed submission:<ts>:<uuid>, with email/project/topic/date
in KV metadata). Records are written before email is sent, so a lead survives
even if delivery fails. Email is no longer the only copy.

Author: julianengel

workers/contact-form/README.md

@@ -10,8 +10,27 @@ transactional emails through MailLayer (`mail.simplebytes.com`):
 2. **Admin notification** to `ADMIN_EMAIL` (`hello@simplebytes.com`), with
    `reply-to` set to the submitter so you can reply directly.
 
+Every valid submission is also stored in the `SUBMISSIONS` KV namespace as a durable
+record (email is no longer the only copy).
+
 The source here was recovered from the live deployment; keep it as the source of truth.
 
+## Reading stored entries
+
+Submissions are written under keys like `submission:<timestamp>:<uuid>`, with the
+email/project/topic/date mirrored into KV metadata for quick scanning:
+
+```sh
+# List recent entries (key + metadata, no full value)
+wrangler kv key list --binding SUBMISSIONS
+
+# Read one full entry
+wrangler kv key get --binding SUBMISSIONS "submission:1720000000000:...."
+```
+
+Records are stored before the emails are sent, so a lead is preserved even if
+email delivery fails.
+
 ## Request shape
 
 `POST` JSON: `{ name, email, project, topic, message, website, turnstileToken }`

workers/contact-form/src/index.js

@@ -84,6 +84,18 @@ export default {
       const projectLabel = PROJECT_LABELS[project] || project;
       const topicLabel = TOPIC_LABELS[topic] || topic;
 
+      // Persist a durable record before sending, so a lead is never lost even
+      // if email delivery fails. Storage problems must not break the response.
+      await storeSubmission(env, request, {
+        name,
+        email,
+        project,
+        projectLabel,
+        topic,
+        topicLabel,
+        message,
+      });
+
       // Confirmation to the submitter.
       await sendEmail(env, {
         to: email,
@@ -118,6 +130,33 @@ function isValidEmail(email) {
   return /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(email);
 }
 
+async function storeSubmission(env, request, fields) {
+  if (!env.SUBMISSIONS) return;
+  try {
+    const submittedAt = new Date().toISOString();
+    // Sortable key: newest entries sort last by timestamp, unique by UUID.
+    const key = `submission:${Date.now()}:${crypto.randomUUID()}`;
+    const record = {
+      ...fields,
+      submittedAt,
+      ip: request.headers.get('CF-Connecting-IP'),
+      country: request.cf && request.cf.country,
+      userAgent: request.headers.get('User-Agent'),
+    };
+    await env.SUBMISSIONS.put(key, JSON.stringify(record), {
+      // Lightweight fields so `kv key list` is useful without reading each value.
+      metadata: {
+        email: fields.email,
+        project: fields.projectLabel,
+        topic: fields.topicLabel,
+        submittedAt,
+      },
+    });
+  } catch (error) {
+    console.error('Failed to store submission:', error);
+  }
+}
+
 async function verifyTurnstile(token, secretKey) {
   if (!token || !secretKey) return false;
   const response = await fetch('https://challenges.cloudflare.com/turnstile/v0/siteverify', {

workers/contact-form/wrangler.toml

@@ -7,6 +7,11 @@ compatibility_date = "2024-01-01"
 ADMIN_EMAIL = "hello@simplebytes.com"
 FROM_EMAIL = "noreply@simplebytes.com"
 
+# Stores every valid submission as a durable record (see src/index.js).
+[[kv_namespaces]]
+binding = "SUBMISSIONS"
+id = "1ef74d0d5a994477848a453437032a46"
+
 # Secrets — set once with `wrangler secret put <NAME>`, never committed:
 #   TURNSTILE_SECRET_KEY      Cloudflare Turnstile secret key
 #   ADMIN_TEMPLATE_ID         MailLayer transactional key for the admin notification email