Learn and master Clay with Clay university

This lesson covers the other path: connecting inboxes you already own instead of buying managed accounts. You probably shouldn't take it. The option is here if you want it, and there are two situations where it's the right call, so this lesson walks through both and what the path costs you in maintenance.

You'll find it at Add email account, where instead of buying managed accounts you choose to bring in your own.

✅ When It's the Right Call

There is one real reason to bring your own, and it's that you want to send from your primary domain. Two situations make that hold up.

The first is warm prospects. Someone registered for your webinar, or emailed and asked you a question six months ago, and now you're back in touch. Low volume, and there's already a relationship, so sending from your real domain is honest and it works.

The second is if you're genuinely enormous. If you already send millions of transactional emails a month, the way a company like Stripe or Ramp does, your primary domain has the reputation and the traffic volume to absorb some outbound without anyone noticing.

Most companies are not at that level, and if you're not sure whether you're that company, you're not.

🔌 The Four Ways In

Once you toggle over and continue, you get four options:

• Gmail through OAuth
• Outlook through OAuth
• Manual SMTP setup
• Bulk CSV upload

Use OAuth. The rule on SMTP is the right one: if you don't know what SMTP is, you should not press this button. It's also the least secure path, because you're handing over a username and a password rather than a token that can be revoked.

You'll also see a note that your credentials get shared with Smartlead, Clay's email integration partner. That's the same infrastructure as the accounts you'd buy in the previous lesson.

🔐 Why There's an Admin Step

Connect a Google account and you'll get a pop-up asking whether you want to enable email warming. That question is where the extra work comes from.

Warming sits in a gray area with the providers. They allow it to happen, but they don't make it easy, and they don't approve apps that do it. Which means a Workspace admin has to go into the admin panel and manually mark Clay Sequencer as a trusted application.

There are a few configuration steps in that modal, done once per workspace. The modal links a video tutorial, which is worth watching, and this step generally requires someone from your IT department to help you out.

🔧 The Maintenance You're Signing Up For

Back in the Email accounts table, the Source column shows which accounts came in through OAuth, which came from SmartSenders, and which were set up manually.

The cost of the OAuth path isn't money. Connections break:

• A user revokes access by accident
• Google pulls a token over something happening in their security
• An admin sweeps every third party grant in the company

Fixing it is one click on re-auth, no problem. The hard part is noticing, because there are no alerts. If a campaign has not been sending for a week, or for a month, you won't know unless you're checking manually.

That's the risk of bringing in your own email accounts: you are responsible for your own infrastructure, so if anything goes down, you are responsible for fixing it.

🔁 One More Time

You probably shouldn't go down this path. The option is here if you want it, and now you know how to set it up.

If you're on the fence, just buy the accounts from us. It's close to the same cost and far less maintenance.

🚀 What's Next

You now know the two narrow cases where bringing your own inbox makes sense, the four ways to connect one, why a Workspace admin has to get involved, and the maintenance you take on by choosing this path.

That's the infrastructure covered. Next we get into campaigns and setting up an actual list of people, and you'll see why we do it in Audience segments instead of traditional Clay tables.

‍