I built SmolMail because I was tired of manually copying info from emails into other apps. Amazon sends a shipping confirmation — I open Google Tasks, type the item name, set the due date. A flight confirmation arrives — I create a calendar event, copy the times, add the confirmation number. A receipt comes in — I add a row to my expense spreadsheet.
SmolMail sits on top of your Gmail inbox. Expand any email, and Claude extracts the structured data — item names, dates, amounts, confirmation numbers. Then one click to send it where it's useful: Google Tasks, Calendar, Sheets, or Drive.
For recurring patterns (e.g., every Amazon shipment), you can create automations that match by sender/subject, extract the same fields, and create actions automatically.
The stack is React + Cloudflare Workers + D1. Extraction uses Claude in two modes: text (sends HTML) or vision (sends a screenshot for emails where the layout matters more than the markup). Extractors run client-side in a sandboxed iframe.
You can try the demo at smolmail.com/demo — no login required, full interactive inbox with sample emails.
I'd love feedback on the UX flow and what email patterns you'd want supported.
narinluangrath•1h ago
SmolMail sits on top of your Gmail inbox. Expand any email, and Claude extracts the structured data — item names, dates, amounts, confirmation numbers. Then one click to send it where it's useful: Google Tasks, Calendar, Sheets, or Drive.
For recurring patterns (e.g., every Amazon shipment), you can create automations that match by sender/subject, extract the same fields, and create actions automatically.
The stack is React + Cloudflare Workers + D1. Extraction uses Claude in two modes: text (sends HTML) or vision (sends a screenshot for emails where the layout matters more than the markup). Extractors run client-side in a sandboxed iframe.
You can try the demo at smolmail.com/demo — no login required, full interactive inbox with sample emails.
I'd love feedback on the UX flow and what email patterns you'd want supported.