Gmail node ignoring "Send As" default - sends from Gmail instead of configured business email

Help me Build my Workflow
,
1

I have Gmail OAuth credentials configured with Hostinger “Send As” defaults set in Gmail settings.

When I manually compose in Gmail, emails correctly send from bu…[email protected].

However, the n8n Gmail node ignores the default “Send As” setting and sends from the Gmail address ([email protected]) instead.

The Gmail node doesn’t have a “From” or “Send As” parameter in the options. How can I force the Gmail node to use my configured “Send As” address?

What I’ve tried:

  • Set business email as default “Send As” in Gmail settings ✓
  • Verified and reconnected Gmail OAuth credentials
  • Checked all available node options (no “From” field exists)

n8n version: 2.0.3 (self-hosted)
Gmail node version: 2.2

Is there a parameter I’m missing, or does the Gmail node not support “Send As” functionality?

I had this before:

| from: | b……@ninjamarketingdigital.com
|
|—:|----|
| to: | o……………@gmail.com
|
| date: | Jan 12, 2026, 1:06 AM |
| subject: | Last note from me |
| mailed-by: | ninjamarketingdigital.com |
| signed-by: | ninj…ngdigital.com |
| security: | Standard encryption (TLS)
| |10pxx10px: | Important according to Google magic. |
|

But suddenly changed to:

|

| from: | Giorgina Villani <giorginavillani338@gmail com>
|
|—:|----|
| to: | Olawalew345@gmail
|
| date: | Jan 13, 2026, 5:06 AM |
| subject: | Testing |
| mailed-by: | gmail.com |
| signed-by: | gmail.com |
| security: | Standard encryption (TLS)
| |10pxx10px: | Important according to Google magic. |

2

This isn’t something you’re missing it’s a limitation of the n8n Gmail node.

Even though Gmail UI respects your default “Send As” address, the Gmail API does not automatically apply it. The n8n Gmail node uses users.messages.send without explicitly setting a from / sendAsEmail, and the node currently doesn’t expose a “From” field. When that happens, Gmail falls back to the primary Gmail address, which is what you’re seeing.

That’s why:

  • Manual Gmail sends → correct domain email

  • n8n Gmail node sends → primary @gmail.com

Workarounds:

  1. Use the SMTP Email node instead (with your domain email + OAuth/App Password)

  2. Use an HTTP Request node to call the Gmail API directly and set sendAsEmail

  3. Create a separate Gmail account / OAuth credential where the domain email is the primary sender

So yes as of now, the Gmail node does not fully support “Send As” behavior, even if it’s configured and verified in Gmail.

[email protected]