If your business runs on Zoho’s productivity suite for daily communication but needs to send thousands of transactional emails (order confirmations, password resets, shipping updates), you already know that Zoho Mail alone is not built for high-volume programmatic sending. That is where configuring Zoho Mail with SendGrid for transactional email routing becomes a practical solution.
SendGrid, now part of Twilio, specializes in email delivery at scale. It offers dedicated IP addresses, advanced analytics, and infrastructure designed for transactional messages. Zoho Mail handles your team’s business communication, while SendGrid takes over the automated, high-volume side. This split keeps your business email reputation separate from transactional sends, which is a best practice that many growing companies overlook.
In this guide, you will learn how to configure SMTP relay between Zoho Mail and SendGrid, set up proper email authentication with SPF, DKIM, and DMARC, handle bounces through webhooks, and monitor delivery performance. Every step includes the actual configuration values so you can implement this in your own environment.
The core of this integration is configuring SendGrid as the outbound relay for transactional messages while keeping Zoho Mail as your primary business email provider. Here is how to set this up from scratch.
Log into your SendGrid dashboard, navigate to Settings, then API Keys, and click Create API Key. Select “Restricted Access” and grant only the Mail Send permission. Copy the key immediately because SendGrid shows it only once. Store it in a secure credential manager.
Use these values in any application or service that sends transactional email through SMTP:
| Setting | Value |
|---|---|
| SMTP Server | smtp.sendgrid.net |
| Username | apikey (literal string) |
| Password | Your SendGrid API key |
| Port (TLS) | 587 |
| Port (SSL) | 465 |
| Port (Fallback) | 2525 |
| Encryption | STARTTLS on port 587 (recommended) |
Port 587 with STARTTLS is the modern standard and typically encounters fewer firewall issues than port 465. Avoid hardcoding SendGrid server IP addresses because their IP pool changes periodically.
In Zoho Mail’s Admin Console, go to Mail Administration, then Email Routing, and select Outbound Gateway. Enter smtp.sendgrid.net as the relay server with port 587. You can route all outbound email or only messages from specific users or groups. For transactional email routing, the best practice is to create a dedicated sender address (such as notifications@yourdomain.com) and route only that address through SendGrid.
This approach keeps your team’s regular Zoho Mail traffic flowing through Zoho’s own servers while transactional messages go through SendGrid’s optimized delivery infrastructure.
When you route email through two different providers, authentication records in DNS need to cover both. Misconfigured authentication is the most common reason transactional emails land in spam folders.
Your domain’s SPF TXT record must authorize both Zoho and SendGrid to send on your behalf. A combined record looks like this:
v=spf1 include:zoho.com include:sendgrid.net ~all
SPF has a 10-DNS-lookup limit. Each include: counts as one lookup, and the included domains may have their own nested lookups. Check your total with an SPF validation tool to confirm you stay under the limit. If you are close, consider using SPF record flattening to reduce lookup count.
SendGrid requires domain authentication through DNS CNAME records. In the SendGrid dashboard, go to Settings, then Sender Authentication, and click Authenticate Your Domain. SendGrid will generate three CNAME records:
Add these CNAME records to your DNS provider. SendGrid handles automatic DKIM key rotation, so you do not need to update these records after initial setup. Zoho Mail has its own DKIM signing configured separately in the Zoho Admin Console under Email Authentication.
With both SPF and DKIM configured for two providers, add a DMARC record to tie them together:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; pct=100
Start with p=none (monitoring only) for at least two weeks. Review the aggregate reports sent to your rua address. Once you confirm that all legitimate mail passes DMARC checks, move to p=quarantine and eventually p=reject. This phased approach prevents accidental blocking of legitimate transactional email during the transition.
A clean routing architecture separates business correspondence from automated transactional messages. This protects your primary domain reputation and simplifies troubleshooting when delivery issues arise.
Consider using a subdomain for transactional email (such as mail.yourdomain.com for business and notify.yourdomain.com for transactional). This creates separate domain reputations. If a transactional sending issue triggers spam complaints, it does not affect your primary business email deliverability.
Set up the subdomain in both SendGrid (for sending) and your DNS (for authentication records). Each subdomain gets its own SPF, DKIM, and DMARC records.
Zoho Mail’s routing configuration in the Admin Console supports conditional routing based on sender address, recipient, or content patterns. You can set rules such as:
This granular control means you do not have to make an all-or-nothing choice. Your Zoho Campaigns email marketing traffic can use its own path, business email stays on Zoho servers, and only transactional messages hit SendGrid.
For applications that generate transactional email programmatically, the SendGrid v3 Mail Send API offers more control than SMTP relay. The API supports JSON payloads with features like dynamic templates, scheduling, and custom tracking categories. A basic API call sends a POST request to https://api.sendgrid.com/v3/mail/send with your API key in the Authorization header.
Use the API when your application needs template rendering, batch sending with personalization, or send-time scheduling. Use SMTP relay when you want simpler integration with existing mail infrastructure or third-party applications that already support SMTP configuration.
Transactional email at volume will produce bounces. How you handle them determines your long-term sender reputation and deliverability rates.
SendGrid automatically categorizes bounces into hard and soft types. Hard bounces (invalid address, domain does not exist) are added to a suppression list, and SendGrid will not attempt delivery to those addresses again. Soft bounces (mailbox full, temporary server error) trigger retries over a period before converting to a hard bounce if unresolved.
You can view and manage suppression lists in the SendGrid dashboard under Suppressions. Export these lists periodically and sync them with your Zoho CRM contact records to keep your data clean across systems.
For real-time bounce handling, configure SendGrid’s Event Webhook. Go to Settings, then Mail Settings, and enable Event Notification. Provide your endpoint URL (such as https://yourdomain.com/api/sendgrid-events) and select the events you want to receive:
SendGrid sends event data in JSON batches every 30 seconds or when the batch reaches 768 KB. Your endpoint should return a 2xx status code within 3 seconds. Failed deliveries retry for up to 24 hours. Secure your webhook endpoint with SendGrid’s ECDSA signature verification to prevent spoofed event data.
When your webhook receives a hard bounce event, the workflow should update the contact status in your CRM, flag the email address in your application database, and log the bounce reason for analysis. For businesses using Zoho CRM, you can trigger a custom function via webhook that updates the contact record’s email status field. This prevents your application from continuing to send to invalid addresses, which would further damage sender reputation.
Visibility into transactional email performance is critical for maintaining high delivery rates. Both Zoho and SendGrid provide monitoring tools, and combining them gives you a complete picture.
The SendGrid dashboard provides an Activity Feed showing individual message status (processed, delivered, opened, bounced, deferred). The Statistics section offers aggregate data including delivery rate, open rate, bounce rate, and spam report rate. Break these down by category if you tag transactional emails by type (order confirmation, password reset, shipping notification).
Aim for a delivery rate above 97% and a bounce rate below 2%. If bounce rates climb above 5%, investigate whether your application is sending to unverified addresses or if a specific email type is triggering spam filters.
Configure SendGrid alerts for unusual patterns. Set thresholds for bounce rate spikes, sudden drops in delivery rate, or increases in spam reports. SendGrid can send these alerts via email. For more advanced monitoring, forward webhook event data to a logging service and build dashboards that track trends over time.
If your organization uses Zoho Analytics, you can pipe SendGrid event data into it for custom reporting. This is especially useful for businesses that want to correlate transactional email performance with e-commerce activity from platforms like Shopify or CRM pipeline stages.
Schedule monthly reviews of your email authentication status. Use tools like MXToolbox to verify that SPF, DKIM, and DMARC records resolve correctly and that neither Zoho nor SendGrid IP addresses appear on major blocklists. Proactive monitoring catches issues before they impact delivery to your customers.
If you are moving from a single-provider setup to this split architecture, plan the transition to avoid disruption.
Start by routing one category of transactional email through SendGrid (such as password resets). Monitor delivery and engagement metrics for a week. Then add order confirmations, then shipping notifications. This incremental approach lets you catch configuration issues early without affecting all transactional email at once.
SendGrid automatically warms new accounts and IP addresses by gradually increasing sending volume. If you expect to send more than 50,000 emails per month, request a dedicated IP address. Shared IP reputation depends on other senders, while a dedicated IP gives you full control over your sender reputation.
For businesses processing more than 500,000 transactional emails monthly, consider SendGrid’s Pro plan which includes a dedicated IP, sub-user management, and priority support. The cost scales with volume, but the deliverability improvements typically offset the investment.
Zoho’s own transactional email service, ZeptoMail, is worth evaluating if you want tighter integration with the Zoho ecosystem and your volume stays under 50,000 per month. ZeptoMail focuses exclusively on transactional email and offers competitive pricing. However, SendGrid provides more advanced analytics, a larger set of API features, and better scalability for organizations sending at high volume. Businesses that already use SendGrid for other applications or need features like IP pool management will get more value from the SendGrid integration. If you are migrating from another email platform, factor in the transition effort for each option.
Need help configuring Zoho Mail with SendGrid for your transactional email workflow? Our team can set up the complete integration for you.
Talk to Our Zoho Experts
High DSO drains cash flow. Discover proven tactics to reduce days sales outstanding, automate your…
On this page Food and beverage manufacturers face a set of operational demands that generic…
Build a custom payment collection portal using Zoho Creator and Razorpay. Step-by-step setup with Deluge…
Our team builds systems that actually work. No fluff, just honest architecture and clean implementation.
