Using Lettrove
lettrove.com is the Lettrove app: where your team designs emails, brings in the people to send them to, sends from your own domain, and sees what happened. These pages cover that app. The rest of this site covers the embeddable editor, the same editor inside your own product; start at the Introduction for that.
| You want to | Read |
|---|---|
| Let Claude, Cursor or another AI assistant work in Lettrove as you | MCP server |
| Bring contacts in from a file, by hand, or from HubSpot | Bringing contacts in · HubSpot |
| Send an email to a list from your own domain | Sending |
| Invite your team and decide who can do what | Workspaces, roles and the activity log |
| Connect other tools | Integrations |
| Know what AI costs and where it is used | AI and your allowance |
| Answer a security review | Security |
How it fits together
A workspace is one team's Lettrove: its emails, templates, brand, audiences, sending domains and members. You can belong to several; everything is kept per workspace, and nothing crosses between them. Within a workspace:
- Emails are designed in the editor, by hand or from a brief with the assistant, and kept with their history. Templates in the gallery are a starting point.
- Audiences are lists of people: imported from a file, typed in, or synced from HubSpot. Each list has the columns you give it, and those columns are the merge tags an email can use.
- Sending goes out from a domain you have verified, as a sender address on it, to the lists you choose: a test to yourself first, then a campaign now or at a time, with delivery, opens, clicks and unsubscribes reported per send and per list.
- Members have one of four roles, and every action that matters is written to the activity log.
Everything the app does is also what the MCP server lets an AI assistant do, with the same permissions you have.