A new row in the sheet becomes a personal email journey. Nobody copies a thing.
A home furniture retailer collects design requests in a Google Sheet. With tinyEmail's MCP Server and Claude Code, every new lead is checked, added, tagged, placed in the right workflow, and sent a first email written just for them. Then the sheet is updated with what happened.
Example scenario. Brand, leads, and figures are illustrative.
240 leads a week, each one copied by hand
Design requests come in from the website, Instagram ads, and the showroom floor. They all land in one Google Sheet. From there, someone on the marketing team moved each lead into tinyEmail, one row at a time.
The work was done in a batch once a day. That meant a shopper who asked about dining tables on Monday morning heard back on Tuesday, often after they'd already found a table somewhere else.
One instruction replaced six manual steps
With the MCP Server connected, Claude Code works directly inside the retailer's tinyEmail account. The team wrote the onboarding rules once, in plain English. Now Claude Code reads the new rows and handles every lead the same way, every time.
See how to set it up →> Check the Design requests sheet for rows with no status. For each new lead: check the email, add them to tinyEmail with tags and their budget and city, enroll them in the workflow that fits their interest and budget, write a personal first email, start the automation, and write the result back to the sheet.
What happens to each lead, step by step
Pick a lead to see how Claude Code handled them. Each one gets a different path, and a lead with a bad email address never reaches your audience.
Every lead lands in the right place
The team wrote four rules. Claude Code applies them to every row, and the tags and custom fields it saves mean each workflow knows exactly who it's talking to.
Dining, living room, bedroom, or home office. Three emails over seven days, all about that room.
An invitation to a free one-hour session with a designer at the nearest showroom.
New tags are added to the existing contact. No second copy, no repeat welcome email.
Nothing is added or sent. The row is flagged so a person can fix it.
Leads hear back while they're still shopping
The first email now arrives minutes after someone asks for help, and it talks about the room, budget, and showroom they mentioned. The marketing team spends its time on the workflows themselves, not on moving rows between tools.
Set it up in three steps
About five minutes, one time.
Get your API key
In tinyEmail, go to Account Settings → API Keys. It's the secure pass your assistant uses, and it's never stored.
Connect Claude Code
Add tinyEmail to Claude Code with your API key. It works the same way in Claude Desktop and ChatGPT.
Write your onboarding rules
Tell Claude Code which sheet to watch and how to route each lead. Start from the instruction in this story.
View the instruction ↑More ways teams use it
Common questions
Do I need to write code?+
No. Claude Code takes instructions in plain English. You describe the rules, and it does the work inside your tinyEmail account.
Can I check the first email before it sends?+
Yes. Add “show me each email before you start the automation” to your instruction, and Claude Code will wait for your go-ahead.
What if a lead is already in my audience?+
That's up to your rules. In this story, existing contacts get new tags and no repeat welcome email, so nobody is added twice.
Is my account secure?+
Yes. Your API key goes straight from your assistant to tinyEmail. The MCP Server never stores or logs it.
Who can use the MCP Server?+
It's available to tinyEmail Enterprise customers. Contact your account team or support through in-app chat to get started.
Let your next lead get a reply before they close the tab.
If you have not set up the tinyEmail MCP yet, watch this tutorial to connect it to ChatGPT or Claude Code and start using it today.
.svg)
.svg){kind=small}
.svg){kind=small}
.svg){kind=small}
