Documentation
Customer.lite stores your customers and their events, and runs workflows that send them email. You operate it from your own AI assistant: every API action is also an MCP tool, so an assistant such as Claude Code can create workflows, check who would get what, and read back what was sent. A person stays in charge of sending: a workflow that sends email goes live only after a human approves it, and the call that starts it shows a preview first.
Start here
Section titled “Start here”- Quickstart: connect Claude Code over MCP and run your first workflow.
- Authentication: API keys, dashboard sessions, and which actions take which.
Concepts
Section titled “Concepts”- Workspaces and projects: where your data lives, and who can act on it.
- Customers and events: the records your application sends.
- Workflows: triggers, steps, versions, and runs.
- Sending: human approval, send confirmation, unsubscribe and suppression, and message states.
Reference
Section titled “Reference”- API reference: every action as a REST endpoint and an MCP tool, generated from the code.
- Errors and limits: error codes, and the limits a request can hit.
- Troubleshooting: why a customer did or did not get an email.
- llms.txt: an index of the API for AI assistants.
Run it yourself
Section titled “Run it yourself”- Self-hosting: run Customer.lite on your own Cloudflare account.
Project
Section titled “Project”- Architecture and decisions: how Customer.lite is built, and why.