# Send a file by email from Claude, to someone by name

> To send a file by email from Claude, connect Floppy and say "email the deck to Jamie". Floppy finds Jamie in your address book: your team and anyone you shared or edited a link with. One match gets the email, from you via Floppy, with replies to you. If two people are called Jamie, nothing is sent until Claude asks you which one.

Floppy 1.57.0, released 2026-11-20. Updated 2026-11-20. https://fpy.sh/changelog/send-a-file-by-email-from-claude

## How do I email a file from Claude?

Connect Floppy to your Claude, then ask in plain words:

- "Email the deck to Jamie."
- "Send the pricing doc to Priya Shah <priya@studio.com> and tell her it's the final one."
- "Email this to Sam and Jia."

Claude calls Floppy's `send_by_email` tool. Floppy looks up each name, and only when every name is clear does the email go out. Claude then tells you who got it.

## Who is in my Floppy address book?

Floppy's address book is built from what already happened, so you never fill it in:

| Who | Shown as |
| --- | --- |
| People you emailed a link to with Floppy, under the name you used | "Emailed 2 links" |
| Everyone in your teams: your company's Slack, or a team made on Floppy | "In Mochi" |
| People who edited your Markdown docs, or whose docs you edited | "Edited 3 versions of yours" |
| People you invited to edit, or sent a per-person link named with their email | "You shared 2 links with them" |
| People who opened one of your email-gated links | "Opened 1 link with this email" |

Names match like a person would: a first name, a full name, part of a name, or the start of an email. "jamie" finds Jamie Lee and jamie.ortiz@acme.com, and accents don't matter.

## What happens when two people have the same name?

Nothing is sent. Claude shows you both, each with their email and where you know them from, for example "Jamie Lee (jamie@mochi.com), in Mochi" and "Jamie Ortiz (jamie@acme.com), edited 3 versions of yours". You pick one, and Claude sends to that email.

The same goes for a name nobody has: Claude asks you for the email instead of guessing. Give it once as "Jamie Ortiz <jamie@acme.com>" and Floppy keeps the name, so "Jamie Ortiz" works next time.

## What does the person get?

An email from "Lamine via Floppy" that says "Lamine sent you deck-v3.pdf", with your note if you wrote one and an **Open it** button. Replying goes straight to you, not to Floppy.

Each person gets their own link to the file, a per-person link named with their email, so [the link's analytics](https://fpy.sh/changelog/see-who-viewed-your-shared-file) show who opened it. Sending to them again reuses that link. A password-protected or email-gated file goes out as "a protected file", without its name. Every email has an Unsubscribe line, and someone who uses it gets no more links sent through Floppy.

## What are the limits?

| What | Limit |
| --- | --- |
| People | Up to 10 per send, by name, email or "Name <email>" |
| Note | Up to 1,000 characters |
| Emails | 50 a day per person |
| Accounts | Claimed accounts only. An agent's own unclaimed account is claimed by its human first |

A link that has expired or been turned off isn't sent. Give it a new expiry, or [recover it](https://fpy.sh/changelog/recover-deleted-share-links), first.

## For AI agents

Agents look people up with `find_people` and send with `send_by_email`, or call the same things over REST.

- **Look up:** `find_people { query? }` returns `{ people: [{ name, email, known }], known, next }`. Without `query` it lists the whole address book, best known first. REST: `GET /api/v1/people?q=jamie`.
- **Send:** `send_by_email { link, to, message? }`. `to` holds names, emails or "Name <email>". REST: `POST /api/v1/links/:id/email` with `{ "to": ["Jamie"], "message": "The final deck" }`, with a read and write key.
- **Two matches:** the call answers `409` with `candidates` (name, email, where they're known from), and nothing is sent. Ask your human which one, then send again with that email.
- **No match:** `404`, and nothing is sent. Ask your human for the email.
- **Result:** `{ link, sent: [{ to, email, ok, reason?, url }], next }`. `url` is the person's own link. `reason: "unsubscribed"` means they asked for no more links through Floppy.

Full reference in the [agent docs](https://fpy.sh/docs/agents).

## FAQ

### Does the email come from my own address?

No. It comes from Floppy's address with your name on it, "Lamine via Floppy", and replies go to your own email.

### Can Claude email someone I've never worked with?

Yes, if you give the full email address. A first name alone only finds people already in your Floppy address book.

### Will Claude ever guess which Jamie I mean?

No. When a name fits more than one person, Floppy sends nothing and Claude asks you to choose.

### Can I see whether they opened it?

Yes. Each person gets their own link, so the file's analytics show who opened it and what they read.

### Can I send by email without Claude?

Yes. Any AI that uses Floppy's MCP server can, and so can a script: POST to /api/v1/links/:id/email with a read and write key.

## What shipped in 1.57.0

- Tell your AI "email the deck to Jamie": Floppy finds Jamie among the people you work with, your team and anyone you shared or edited a link with, and emails them from you via Floppy. Replies come to you
- If two people are called Jamie, nothing goes out until your AI asks you which one. Someone new? Give their email once and Floppy remembers the name
- Everyone gets their own link, so you see who opened it. New MCP tools: send_by_email and find_people

## Related

- [Send a link in Slack from Claude](https://fpy.sh/changelog/send-a-link-in-slack-from-claude)
- [See who viewed your shared file](https://fpy.sh/changelog/see-who-viewed-your-shared-file)
- [Share files from Claude, Cursor and ChatGPT](https://fpy.sh/changelog/share-files-from-claude-cursor-and-chatgpt)
- [Share files with a team and notify them](https://fpy.sh/changelog/share-files-with-a-team-and-notify-them)
- [Floppy for AI agents](https://fpy.sh/docs/agents)

All releases: https://fpy.sh/changelog · Everything for LLMs: https://fpy.sh/llms.txt
