How to Use Warmy to Warm a New Domain With Your Templates

The short answer: if campaign mail is moving to a new sending domain, give Warmy 2 to 4 weeks before the first real send, the range in its own campaign preparation article, on a plan that starts at $49 a month (pricing page, checked on 26 October 2026). The steps: connect the mailbox, choose the slow temperature, import your HubSpot templates so the warm-up carries your real content, share Google Postmaster data, test placement against the providers your list uses, then put Warmy's placement checker inside the first campaign and let an n8n workflow report the weekly test.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

A new domain has no history, and a mailbox provider treats a sudden volume of mail from it as a warning sign. Warm-up gives the domain a record before your list sees it. What Warmy includes and costs is in the Warmy glossary entry.

Three things to settle before you connect:

1. How much of the warm-up is your content. With your templates assigned and no topic chosen, half of the warm-up emails use your templates; with a topic, a quarter; with "Use only my own templates" switched on, all of them, per the template article. For example, a mailbox sending 40 warm-up emails a day with templates assigned and no topic sends 40 / 2 = 20 of yours.
2. What you already have. The templates your team sends from HubSpot, and the Google Postmaster account for the domain if one exists. Warmy's Postmaster article notes that Google shows basic charts only from about 100 to 200 messages a day to personal Gmail accounts.
3. The reading that says go. The ISP score from Warmy's placement test runs from 0 to 10: 8 to 10 generally means good deliverability, 4 or below means significant issues, according to the test article.

Before you start

• A mailbox on the new domain, with SPF, DKIM and DMARC records in place.
• A Google Workspace administrator, who has to approve Warmy's app, or the Microsoft 365 equivalent.
• The 7-day trial: one mailbox, 15 to 50 warm-up emails a day, no card, per the trial guide. Steps 1 to 5 run on it and cost nothing, which is enough to prove the setup before any plan is bought.

Step 1: Connect the mailbox

In Warmy, click Connect, choose Google Workspace and copy the Google App ID it shows. Your administrator opens App Access Control in the Google Admin console, clicks Configure new app, searches for that App ID, selects Warmy and approves access, as the connection article describes. Back in Warmy, finish the connection. Then run the Health test on the mailbox dashboard, which the campaign preparation article points to for checking the DNS records.

Step 2: Choose the slow temperature

Temperature is Warmy's word for how many warm-up emails a mailbox sends today. Open Mailboxes, pick the mailbox, open its settings and choose slow, medium or fast. The temperature article recommends slow and warns that fast mode can hurt your reputation in some cases. A new domain has nothing to gain from hurrying.

Step 3: Import your HubSpot templates

Open the Workspace tab, then Settings, then Integrations, click Connect next to HubSpot, log in and authorise Warmy. In the Templates tab, open List, click Add New and choose HubSpot; the templates arrive after a short delay, per the HubSpot article. No HubSpot? Paste the text into Warmy's plain-text or HTML editor instead.

The template article asks for 5 or more templates, each assigned to the mailbox. Every template is reviewed before use, usually within one business day. In plain text you can add snippets for the recipient's name and a random string, plus spintax with 2 to 6 options per block, so the same template does not repeat word for word. Click Save & Analyze for a Template Checker score out of 100 before you assign it.

Step 4: Share Google Postmaster data

In Google Postmaster Tools, add the domain, verify it with the DNS record Google gives you, open Manage domain, then Manage users, and add the address Warmy shows you, as the Postmaster article explains. Warmy then shows delivery errors, authentication, compliance status and spam rate next to its own domain reputation score.

Step 5: Test placement against your list's providers

At the bottom of the mailbox dashboard, open the Email Deliverability Test and pick the providers your list uses: Gmail, Outlook, Yahoo and Zoho for consumers, Google Workspace, Microsoft 365 and SMTP for businesses. Results come back per provider as Inbox, Spam, Promotions or Unreceived. An automatic test is switched on for new accounts and spreads its runs across the week, per the test article; look at the providers that matter to your list first.

Step 6: Put the checker inside the first campaign

When the score holds, add Warmy's checker to the real send. Its campaign placement article has you set a duration (one day by default, seven at most), the number of tracking addresses per provider (10 by default, 50 at most), the providers and the tracking type. Warmy generates the tracking addresses; mix them into the campaign list among real recipients. Yahoo and custom SMTP are not supported.

Step 7: Let n8n report the weekly test, and a person read it

In n8n, open Settings, then Community Nodes, and install the package n8n-nodes-warmy-io. The install asks you to acknowledge unverified code from a public source, so do it on an instance your team controls. In Warmy, create an API key under Workspace, Settings, API Keys, and add it in n8n as a Warmy API credential, per the n8n article.

Build three nodes: a schedule trigger once a week, the Warmy node's Deliverability Checker running a check, and a message to Slack with the inbox and spam result per provider. The node can also change a mailbox's warm-up speed; leave that action out. The workflow reports, and the person who owns the send reads the result and decides whether the campaign goes out on schedule.

Reading the first month

Warmy's results article expects noticeable improvement for a new domain within 3 to 6 weeks and asks you to keep warm-up as the only activity in the first weeks. Once you do send, stay under the provider's daily limit for warm-up and campaign mail together: the usage article uses the example of a free Gmail account limited to 500 a day that sends 250 cold emails, leaving no more than 250 for Warmy.

Warnings from Warmy's help centre

• Own templates only, none approved. If "Use only my own templates" is on and no approved template is assigned, warm-up stops.
• Mass sends too soon. The results article says early volume can damage the domain's reputation.
• Switching off the automatic test. At workspace level it is handled by Warmy support on request; per mailbox or domain you can do it yourself.
• Unsupported providers in campaign tests. Yahoo and custom SMTP are excluded from the campaign checker.

Check one thing before the trial ends. The method above rests on warming with your own templates, and the trial includes that feature, while Warmy's plan article reserves template warm-up for its higher tiers; a trial that shows the upper tier's feature is selling the upper tier, so ask on the call whether the plan you are quoted keeps it.

FAQ

Can I send my own emails during warm-up?

Yes, within your provider's daily limit for both together. For a new domain, the usage article recommends waiting at least two weeks after connecting before campaigns.

Will warm-up mail fill my inbox?

No. Warmy reads the warm-up emails, pulls them out of spam, replies in threads and archives them after a delay, according to the trial guide.

Can I warm the HubSpot sending itself, not only a mailbox?

Warmy documents a HubSpot rotation setup that runs in n8n and moves seed contacts from a pool list into a warm-up list inside HubSpot each day. It needs a HubSpot service key with list permissions and an existing sync workflow, so treat it as a second project after the mailbox is warm.