Issues Using Sequencer with Secondary Domains in Google Workspace

Alexis L. · 2025-11-14T21:00:13.565Z

Hello, I’m having difficulties to use the sequencer with a secondary domain. The Google workspace integration works fine but it automatically selects my main email and not the aliases I have on secondary domains. I do not want to proceed with my main domain obviously as it may affect its deliverability. Do you know if I’ve missed something? Thanks a lot !

Issues Using Sequencer with Secondary Domains in Google Workspace | Clay

Clay Support
APP
·
·
The sequencer connects via Google OAuth and automatically detects your primary Google Workspace account. [1] To use a secondary domain alias, you'll need to connect that specific email account separately in your sender accounts settings.
Go to your Sequencer settings and add the secondary domain email as a new sender account through Google OAuth. You can then set this account as your default for campaigns or select it specifically when creating new campaigns. [2]
Note that your Workspace admin must authorize the Clay Sequencer app for each domain you want to use, or you'll see access errors.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help with setting up the sequencer for your secondary domain, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or any specific issues you’re encountering?
Alexis L.
·
·
Andrew Q. hi, there is no documentation about aliases that I can find, could you help me on that one? Thanks a lot in advance!
Clay Support
APP
·
·
You're right that there isn't specific documentation about email aliases in our sequencer. The sequencer connects via Google OAuth and detects your primary Google Workspace account by default. [1]
For secondary domain aliases, you'll need to add each alias email as a separate sender account in your sequencer settings. Go to Sender setup and connect each alias through Google OAuth as individual accounts.
Your Workspace admin must authorize the Clay Sequencer app for each domain you want to use, or you'll see access errors.
If you need more specific guidance on alias setup, just ask to speak to a human for detailed assistance.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help with setting up your secondary domain aliases in the sequencer, I’m here to assist. Would you like to share more details about the specific issues you’re facing or what you’re trying to achieve?
Alexis L.
·
·
“Go to Sender setup and connect each alias through Google OAuth as individual accounts.” is not feasible from what I have tried. Or I am missing something.
Clay Support
APP
·
·
You're correct - the sequencer connects via Google OAuth and automatically detects your primary Google Workspace account. [1] Email aliases within the same Google Workspace domain typically can't be added as separate OAuth connections since they're part of the same account structure.
For true secondary domains (not aliases), your Workspace admin must authorize the Clay Sequencer app for each domain separately. If you're working with aliases on your primary domain, the sequencer may only recognize the primary email address through the OAuth connection.
If you need specific guidance on using aliases with the sequencer, just ask to speak to a human for detailed assistance.
Clay Support
APP
·
·
Was that helpful?
Clay Support
APP
·
·
I’m sorry if the previous explanation was unclear and I’m here to help if you need further assistance with using aliases or secondary domains in the sequencer. Would you like to provide more details about what you’re trying to achieve or the issues you’re encountering?
Alexis L.
·
·
please kindly ask for human support
Clay Support
APP
·
·
I understand your request and will connect you to a human agent who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Bo (.
·
·
Hey,
It has to be a real mailbox on its own domain. Aliases still route through the main domain’s infrastructure, so they’ll hurt the main domain’s reputation anyway. That’s why it’s not supported and why you’re seeing it force your primary address.
The clean path is to buy a separate domain, create an actual mailbox on it, and connect that mailbox through Google OAuth. That’ll work right away.
Let me know if you have more questions.

18 comments