Apollo.io Mailbox Setup: How to Link and Warm Up Email

Nothing else in Apollo works until a mailbox is linked. Sequences will not send, replies will not be detected, and the engagement side of the product is effectively switched off.

It is also the step where a bad decision costs the most later. Sending cold email from a domain you rely on for invoices and support is the kind of mistake that only becomes obvious months afterwards, when your billing emails start landing in spam.

So this guide covers the linking steps, then warmup, then the domain work that sits underneath both. Do them in that order and the rest of Apollo behaves.

How do you link a mailbox to Apollo?

Apollo's current documentation gives the path as Settings, then Email setup and health, then Mailboxes, then Link mailbox. Some of their older help pages show a shorter Settings then Mailboxes route, so if the labels differ on your account, the screen has moved rather than disappeared.

Linking a Gmail or Outlook mailbox

1. Open the mailbox screen — Launch Apollo and click Settings, then Email setup and health. Click Mailboxes, then click Link mailbox.
2. Pick your provider — Click Gmail or Outlook, or choose Other for a custom server. Apollo names Gmail as its preferred provider for full functionality.
3. Agree and connect — Check the box to agree to Apollo's terms of service, then click Link mailbox.
4. Sign in and consent — If you are already signed in, select the account you want to link. Otherwise sign in, then review and agree to the permissions requested.
5. Repeat for other mailboxes — Run the same steps again for each additional mailbox. Each person has to sign in and consent for their own mailbox.
6. Add an alias if you use one — Go back to the mailbox list, click the overflow menu beside the mailbox, then click Refresh aliases.

Apollo is clear about the scope of what it gets. The permissions apply only to the person who authorises the connection, and Apollo can send email and sync email and calendar activity only for the mailbox that was connected. For Outlook it uses delegated permissions rather than application permissions, so connecting one mailbox does not give it access to every mailbox in the tenant.

How many mailboxes can you link?

Apollo publishes the limits by plan, and they matter if you were planning to spread volume across several senders.

Apollo notes that teams on legacy plans may see different limits, and suggests checking your own plan details in the product. Their pricing page also states that non-paying accounts can only connect Gmail accounts, and that connecting Microsoft or other providers requires a paid plan.

Why won't my mailbox connect?

Apollo documents a specific troubleshooting list, and most connection failures are one of these rather than something exotic.

• It is a Google group, not a mailbox. Apollo states Google groups are not supported and linking one produces an error. Use an individual mailbox.
• Someone else already linked it. Each unique mailbox can only be linked to one Apollo instance at a time. Unlink it from the first account first.
• The address contains an unsupported character. Apollo lists patterns it treats as invalid, including doubled dots or hyphens around the at sign.
• Your provider is POP only. Apollo's third-party sync provider for non-Gmail mailboxes does not support POP or POP3. Most providers that offer POP3 also offer IMAP, which does work.
• A stray Google SPF record is misrouting you. If Apollo sends you to a Google login while linking a Microsoft mailbox, their docs suggest asking your IT admin to remove a Google SPF TXT record from DNS and trying again.
• Microsoft needs admin consent. For enterprise Entra ID accounts, a Microsoft 365 admin may need to grant tenant-wide admin consent to Apollo before anyone can connect.
• Empty mail folders break the sync. Apollo's docs recommend making sure each folder has at least one message and deleting empty folders, because the sync provider can disconnect a mailbox otherwise.

With the mailbox connected, the next job is convincing mailbox providers that mail from your domain is worth delivering. That is two things: authentication and warmup.

What is email warmup, and does it actually do anything?

Apollo describes warmup as connecting your mailbox to third-party providers that send messages from it into a private network of inboxes around the world, which then open and reply to those messages. The point is to simulate real email traffic so mailbox providers see a pattern of trusted sending.

Two things Apollo says about warmup are worth knowing before you turn it on. It runs through Warmbox.ai, a third-party provider, and Apollo states it does not control or take responsibility for that service. And the warmup messages are system-generated test messages, not your sequences or templates, so nothing you wrote goes into that network.

Apollo also says warmup is available on select plans only, and that it only works on mailboxes already connected to Apollo. Link first, warm second.

How do you set warmup up?

Turning on email warmup

1. Open the same screen — Launch Apollo and click Settings, then Email setup and health. Toggle Start warm up beside the mailbox you want to warm.
2. Authorise it — Apollo recommends clicking Sign in with Google and agreeing to the terms. The alternative is entering your email address and a third-party app password, then clicking Check connection.
3. Choose a pattern — Progressive gradually increases volume over time and is what Apollo recommends. Flat sends a consistent volume, useful if the inbox is already warm. Randomized varies the volume.
4. Set an end date — Apollo recommends a minimum of two weeks for good results.
5. Set the daily numbers — Apollo recommends a minimum of 10 emails per day and a maximum of 40, and states the maximum can be no higher than 50.
6. Set the reply rate — Apollo recommends 30 percent, and states this can be no higher than 45 percent.
7. Start it — Click Warm up mailbox. To check progress later, return to Settings, then Email setup and health, and review the warmup status beside the mailbox.

If you use the app password route rather than signing in with Google, note Apollo's warning that a third-party app password is not your normal email password, and that enabling app passwords on Gmail requires two-factor authentication. On Office 365, Apollo says SMTP AUTH has to be enabled in your email app settings or warmup cannot run at all.

What if deliverability drops while warming up?

Apollo splits the answer by mailbox age, which is a more useful distinction than most advice offers. For a new mailbox with little sending history, they say to keep warmup running and troubleshoot the dip, because stopping early can itself hurt your sender reputation.

For an established mailbox with real sending history, they say minor fluctuations usually do not need a pause. Check domain authentication, deal with bounces, reduce outreach volume if needed, and only pause warmup if the decline continues over several days.

The domain work Apollo cannot do for you

This is the section people skip, and it is the one that decides whether anything lands. Apollo states plainly that it does not operate its own email servers. Messages go out through your connected provider, which means authentication is configured at your provider and DNS host, not inside Apollo.

Their documentation names three records to configure for every domain or subdomain you send from: SPF, which identifies who is allowed to send for your domain; DKIM, which adds a cryptographic signature receivers can verify; and DMARC, which tells receivers what to do when the first two fail and gives you reporting.

Apollo also gives a direct instruction that a lot of people ignore: never send cold emails from your primary domain. Use a separate outreach subdomain, because each subdomain carries its own reputation and that gives your main domain a layer of protection. They are equally direct that the subdomain is still connected to the parent, so bad behaviour on the subdomain still puts the root domain at risk.

How much can you safely send?

Apollo's deliverability documentation recommends no more than 50 emails per day per mailbox. Their mailbox setup guidance goes slightly further and suggests starting conservatively at around 50 per day and 6 per hour.

They also note that sending too much too fast, particularly from a new or untrusted domain, can trigger spam filters or cause providers to throttle you. Spreading volume across multiple linked mailboxes or domains is their recommended way to grow without pushing any single sender past what it can carry.

If that felt like a lot of infrastructure

Add it up. A mailbox connection, a permissions consent, an alias decision, three DNS records, a tracking subdomain, a warmup pattern with four numeric settings, a two-week wait, and a daily sending cap to respect. That is real infrastructure work, and none of it has written a single sentence to a prospect yet.

Set-up work like this is exactly what we removed at Sistava. Rather than assembling a sending stack and testing the path, you hire an AI Employee and tell it in plain English what you want handled. It has its tools connected already, it asks you when it is unsure, and it sets itself up.

To be fair to Apollo here, the deliverability suite is one of the genuinely strong parts of the product, and the documentation above is more candid about the risks than most vendors bother to be. If you are running outbound at volume across a team, that control is worth owning. If you are one person who wants a few good conversations a week, it is a lot of machinery to keep upright.

Sources

• Apollo Knowledge Base, Link Your Mailbox to Apollo
• Apollo Knowledge Base, Use Email Warmup to Improve Deliverability
• Apollo Knowledge Base, Email Deliverability Best Practices
• Apollo Knowledge Base, How to Do Cold Emailing Right with Apollo
• Apollo.io, Pricing plans and FAQ