We Said Claude Couldn't Send Email. It Can Now.

Short answer, as of August 24, 2026: Claude's native Gmail connector sends email. It also replies, replies-all, and forwards. For four months this post said the opposite, and it was right when we wrote it. It is wrong now, so here is the correction and the honest current picture.

We could have quietly edited a few sentences. We are not going to, because the whole argument of this post was one capability gap, and that gap is gone. A comparison post that survives the thing it compares is not a comparison, it is an advertisement.

What actually changed

When this went up in April, the native connector's tool surface ended at drafts. create_draft, update_draft, list_drafts, and nothing after it. No send, no reply, no forward. We re-checked on August 7 and again on August 11 and it still read that way both times.

On August 24 we enumerated it again and it reads:

• send_message, which sends a new message and sends an existing draft when you pass it a draftId
• reply, with a replyAll flag
• forward, with an optional comment
• plus trash, untrash, spam, unspam, and the sensitive-label tools

So the exact sentence this post was named after, "it has no tool to send that draft", is now false. Anthropic shipped the verbs. That is a real improvement and it closes the most frequently cited limitation of the native connector.

The corrected comparison

Both columns are what each connector exposes as tools, enumerated on August 24, 2026. Rows move. The date is there so you can tell how stale this table is when you find it, and this particular table has now moved twice in a month.

What is left, stated without inflation

Three rows. That is the honest count.

Deleting a draft. The native connector still has no way to remove a draft it created. If your workflow generates drafts speculatively, it accumulates them and you clean up by hand. This is a small gap and we are not going to pretend otherwise.

Attachments. Ours saves an attachment straight to Drive server-side, so the binary never enters the conversation. The native connector hands attachments back through the context window, which on a large PDF is the difference between a working session and a full one.

Multi-account, which is the one that actually matters. The native connector authorizes one Google account. If you live in a work inbox and a personal one, you disconnect and reconnect to move between them. Ours holds several at once and routes per call, so "check both inboxes and reply from the right one" is a single prompt.

That is the current Gmail story. One meaningful differentiator, two small ones. If Gmail alone is your use case and one account covers it, use the native connector. It is free, it is first-party, and it now finishes the job.

Where the gap is still wide

Gmail is no longer where we win, and it would be dishonest to keep implying it is. The gap has moved to the services the native connectors do not cover at all:

• Sheets. No native cell-level editing. Ours reads, updates, appends, and manages tabs.
• Slides. Native Drive creates an empty deck. Nothing native writes content onto slides.
• Docs. Native reads. Ours creates, writes, and batch-updates.
• Contacts and Tasks. No native connector at all.

If your workflow ends in a spreadsheet or a deck, that is the comparison worth reading, not this one.

The part we want to keep from the original post

This post already contained the method that caught it, which is why we are keeping the section.

We originally blamed a missing gmail.modify scope for the send gap, and the bug report we cited said the same. That was wrong reasoning even when the conclusion was right. A scope is invisible from the outside, inferred rather than observed, and it moves without an announcement. That same report listed "manage drafts and send emails" among the granted scopes, on a connector that at the time had no send tool. Scope and capability come apart in both directions, and neither predicts the other.

So we stopped reasoning from scopes and started enumerating tools, and writing down the date we checked. That is the only reason this correction took thirteen days instead of six months. The method worked. We just have to keep running it.

What we would tell you to do

Connect the native Gmail connector first. It is free and for a lot of people it is now enough.

Come to DataToRAG when you hit one of the walls that is still real: more than one Google account, or a workflow that has to write into Sheets, Docs, or Slides.