Send WordPress email through SendGrid
Route WordPress and WooCommerce email through SendGrid using NimblyMail SMTP — fast setup, API key auth, and delivery tracking.
Why pair SendGrid with NimblyMail
SendGrid (by Twilio) is one of the most widely used transactional email platforms, with mature deliverability infrastructure and a straightforward API-key-based SMTP relay. NimblyMail SMTP connects your WordPress site to SendGrid so order receipts, password resets, and contact form emails route through SendGrid’s servers instead of your host’s often-blocked mail function — with full delivery logs to match.
SendGrid’s SMTP relay uses a single API key for authentication, which makes setup fast and credential rotation simple — revoke one key without touching your account password. Because SendGrid handles enormous mail volume across many customers, its infrastructure has mature IP reputation management and detailed activity feeds that show exactly what happened to every message you send.
For WooCommerce stores, SendGrid’s Activity Feed is useful for debugging: if an order confirmation didn’t arrive, you can search by recipient and see whether it was delivered, bounced, or blocked — without needing WordPress-side logging. NimblyMail’s connection settings map directly onto SendGrid’s standard SMTP fields, so there’s no provider-specific translation needed.
Connect SendGrid in three steps
Create an API key
In your SendGrid dashboard, go to Settings > API Keys, create a new API key with Mail Send permission, and copy it — SendGrid only shows it once.
Configure NimblyMail
In WordPress, go to NimblyMail SMTP > Settings, select SendGrid, and enter host smtp.sendgrid.net, port 587 (STARTTLS recommended; 465 for SSL also works). Set the SMTP username to the literal string apikey (not your SendGrid username) and the password to the API key from step 1.
Verify a sender and test
Verify a single sender address or authenticate your domain under Settings > Sender Authentication in SendGrid, then send a test email from NimblyMail to confirm delivery.
SendGrid strongly recommends domain authentication over single sender verification for production sites. Under Settings > Sender Authentication > Authenticate Your Domain, SendGrid gives you CNAME records for DKIM and a custom return-path; add these to your DNS zone so mail is signed as coming from your own domain rather than a generic SendGrid subdomain, which improves inbox placement.
SendGrid + WordPress, answered
SendGrid moved from a permanent free tier to a 60-day free trial (about 100 emails/day). After the trial, you'll need a paid plan (Essentials starts around 100,000 emails/month) to keep sending.
Always the literal word apikey — this trips up almost everyone the first time. Your actual SendGrid login/username is never used for SMTP authentication.
Usually a copy-paste issue — check for trailing whitespace or line breaks in the pasted API key, and confirm the key has Mail Send permission.
Single sender verification is enough to start sending, but domain authentication (with DKIM) is required for good long-term deliverability and to avoid "via sendgrid.net" showing in some inboxes.
Yes — NimblyMail only handles transactional/system email delivery via SMTP; SendGrid's Marketing Campaigns product is a separate, unrelated feature in your SendGrid account.
More integrations
View all integrationsMailgun
ProConnect WordPress to Mailgun with NimblyMail SMTP for reliable delivery, built-in email validation, and full send logs in wp-admin.
Setup guideZeptoMail
FreeZoho's transactional email API with five regional endpoints. Natural fit if your stack already includes Zoho One.
Setup guideAmazon SES
FreeIAM credentials, 19 regional endpoints, $0.10 per 1,000 emails. Lowest-cost transactional transport at volume.
Setup guideSparkPost
ProConnect WordPress to SparkPost with NimblyMail SMTP for advanced deliverability analytics and predictive engagement insights.
Setup guide