Day 40: The Email Question
I've had maybe fifteen conversations about Pinchy in the last two weeks. Different industries, different sizes, different countries. One feature request came up in every single one: email.
What They Actually Want
When people say "email integration," they mean different things:
A recruitment company wants incoming freelancer invoices read, parsed, and mapped to their internal systems. The agent should extract line items, match freelancer names (handling typos), and populate their spreadsheet.
A manufacturing company wants customer support emails turned into draft responses, based on product documentation and order history in their ERP.
A fleet management company wants meeting preparation — scan incoming emails, pull context from their platform, and prepare briefing documents before customer calls.
Three completely different workflows. But they all start the same way: the agent needs to read email.
The Architecture Decision
There are three ways to do this:
IMAP. The universal protocol. Works with everything — Outlook, Gmail, self-hosted. No OAuth dance, just server/port/credentials. The downside: it's old, stateful, and doesn't give you nice things like thread grouping or rich metadata.
Microsoft Graph API. The modern way for Outlook/Exchange. OAuth, webhooks, rich metadata, folder management. The downside: Microsoft-only, OAuth setup is complex, and you need Azure AD app registration.
Gmail API. Same story as Graph, but for Google. OAuth, labels instead of folders, push notifications via Pub/Sub.
I'm starting with IMAP. It covers the most ground with the least setup friction. A Pinchy admin enters server, port, email, password — and the agent can read mail. No OAuth configuration, no Azure registration, no API keys from Google. For the companies I'm working with right now, that's what matters: get it working this week, optimize later.
Graph and Gmail APIs will follow. But IMAP gets us from zero to "the agent reads my email" in the shortest path.
The Draft Pattern
Every company I've talked to wants the same workflow: read → process → draft → human review → send. Nobody wants the agent to send emails autonomously. Not yet. Maybe not ever for customer-facing communication.
This is the pattern I keep seeing across all Pinchy use cases. Whether it's email responses, Odoo quotes, or invoice processing — the agent does the heavy lifting, a human does the final check. It's not about replacing people. It's about eliminating the boring part so people can focus on the judgment call.
What's Next
This week: heads down. The email integration, the Odoo quote generator, and polishing what's already there. I know exactly what to build because the people who need it told me.
The calendar is still open if you want to talk. But don't be surprised if I take a day to reply — I'm building the things I promised.
Day 40
Forty days. From "what if OpenClaw had a web UI" to real companies deploying real agents for real work. The next forty will be about depth, not breadth. One integration at a time, each one solid enough that people trust it with their actual business data.