Hey!
I have an alias set for my email account, but it seems that I can NOT make n8n send an email from that alias address, I can just pick a “Sender Name”, which is not what I want.
Is it possible to use the alias address? Thanks.
It looks like your topic is missing some important information. Could you provide the following if applicable.
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
Recent similar questions here:
- Gmail node: Ability to select "send as" email address - #3 by ianandersongray
- Send Gmail mail with an Alias?
I think the ideal is to add the credentials for each alias and using separate nodes for each alias.
1 Like
Hi @Malik_Mahjooba,
The Gmail node in n8n doesn’t fully support sending from aliases. Try these alternatives:
- Use Email Send node instead of Gmail node:
- Create new credentials using SMTP
- Server: smtp.gmail.com
- User: your main Gmail address
- Port: 465 (SSL) or 587 (TLS)
- In the “From” field, use your alias address
- If you must use Gmail node:
- Consider creating a separate Gmail node credential specifically for the alias
- This may require setting up app passwords in your Google account
- Alternative workaround:
- Create a new Google account using your alias address
- Set up forwarding rules as needed
- Connect this dedicated account to n8n
Gmail’s API has limitations on sending as aliases that affect n8n’s implementation.
If my answer helped solve your issue, please consider marking it as the solution! A like would make my day if you found it useful! 
3 Likes
Actually those solutions don’t solve the problem
It’s a limitation from the API.
The only solution that I see is setting up different credentials and using them separately.
Hello, I couldn’t find the relevant solution.
Also, what do you mean by that? How can I set that up?
Create n8n credentials for each email alias.
Account 1, account 2…
Then when you want to use an alias, simply use the correct credentials.
Hmm, I don’t quite understand.
How could I create an alias when I set-up a GMAIL credential?
I am quite new to this.
An alias is actually another account, isn’t it?
You have authorized the Account A to be use by Account B as an alias.
Two separate accounts = two credentials
Hmm, its not really 2 credentials.
In the end, when I am going to login to my google account after setting up Client ID and Client Secret–I cannot login with an alias account (I THINK).
Yes. That’s what I know as an alias.
Another account.
I think you got it wrong then my friend.
What do you call an alias?
Can you give examples?
For example my main email is
[email protected] I then have alias such as [email protected] so that I can recieve emails from aliases to my main.
I see. Two different accounts, then.
You can create credentials for those 2 accounts.
Do you understand that?
I solved it with the “Email” node instead. Required 2fa, app password etc, but wasn’t pretty hard to setup. Thanks.
That’s interesting. Can you share what you did?
i thought it wasn’t possible because you can’t “fake” another account.
But apparently you did something different there. Mind sharing the workflow with the community?
More people are interested in this alias solution.
Hi again. I just used the Email node, and set-up the exact same things.
Pretty straightforward.
Yes, I understand that. But since it’s probably a limitation from GMail, i’m curious to how you were able to make it work.
GMail shouldn’t allow for someone to “fake” an alias. It should be an account you have access to. I thought it was impossible, but somehow you managed to achieve it.
Would you mind sharing your workflow so I can test here?