Programmable Email Workflows
MailScript
Rules, scripts, and actions that let software act safely on your inbox. An agent product shipped before agents were the pitch.
The product I founded MailScript to build.
Email is where real work still lands: invoices, contracts, approvals, support, intros, and every operational exception. People handle it by hand, or with filters too weak to matter.
MailScript made the inbox programmable the way people actually think: rules, scripts, and actions. If a message is from this person, carries this attachment, matches this pattern, then label it, extract the data, call an API, route it, trigger the next workflow.
The hard problem was never automation. It was authority. Email holds money, legal commitments, and secrets, and an automation that gets it wrong does real damage. So the product was the permission model: constrained, inspectable, reversible, with the user always knowing what the system may do and why.
That is the agent problem, shipped before agents were the pitch. Intelligence is not the hard part. Deciding where it is allowed to act is.
Gallery
- An automation in place: when a message matches the rule, MailScript acts on it without you.
- An action firing across systems: a matching email routed straight into a Discord channel.
- Email as code: workflows you can script, version, and deploy, because serious automation deserves serious tooling.