SystemeScale
πŸ“– Help Pages Back to platform Support
Help Center β€Ί Email Marketing β€Ί How to send emails with your SendGrid account
βœ‰οΈ Emails

How to send emails with your SendGrid account

πŸ“… Last updated: June 2026
⏱ 2 min read
βœ… All plans

In this article, you will learn how to bridge your personal SendGrid server infrastructure to SystemeScale to manage your outbound marketing campaigns and automated newsletters.

What you will need:

  • A SystemeScale account
  • An active SendGrid account
  • A custom domain name with access to its DNS zone registry
  • A secure SendGrid API key

Understanding the SendGrid hybrid architecture

SendGrid is an external enterprise customer communication platform built for cloud-based transactional and marketing email delivery. It offers powerful optimization resources that improve your overall delivery metrics, helping your outbound messages reach your contacts' primary inboxes rather than dropping into their junk filters.

By connecting your private account, you utilize SystemeScale as the primary administrative dashboard and creation canvas to write your newsletters and sequence campaigns, while the underlying delivery transmission executes entirely through your personal SendGrid server architecture.

ℹ️
What is an API Connection?
An API (Application Programming Interface) is a secure communication bridge that allows two distinct software ecosystems to share data parameters and execute server commands back and forth seamlessly.

Step 1: Link your SendGrid API key token

To integrate your external delivery server with your workspace environment, you must map your secure connection token:

1
Generate your server token
Log in to your SendGrid account portal, navigate to the API settings layout, and generate a new key with Full Access permissions string parameters.
2
Plug the key into your workspace
Open your SystemeScale workspace settings and enter the key token inside your email configuration tab fields. Follow our explicit step-by-step connection guide.
πŸ”‘
How to generate a SendGrid API key and add it to SystemeScale
Need the exact click-by-click interface path to generate and plug your secure SendGrid token string into your profile panel? Read our configuration tutorial.
Read API Token Guide β†’

Step 2: Authenticate your custom domain name records

Whether routing through our native platform clusters or linking your private SendGrid servers, authenticating your custom domain name records is an absolute requirement to ensure proper inbox delivery success.

Method A: Authenticating standard native email routing

If you are not deploying an external SendGrid server framework and prefer to use our native optimized mail relays, our platform automatically generates three (3) unique CNAME cryptographic record strings inside your workspace. You must log into your domain register panel and copy-paste these records directly into your domain's active DNS zone layer.

Once your entries are saved inside your web host console, you must notify our technical support team. Our engineers will verify the records to ensure proper configuration alignment, activate your domain token, and approve your account for live broadcasting.

πŸ”‘
How to authenticate your domain name for email sending
Ready to generate your native platform CNAME tokens and connect your business domain directly into your host dashboard? Follow our master DNS guide.
Read Authentication Guide β†’

Method B: Authenticating domain records inside your SendGrid panel

If you are routing transmissions through your personal SendGrid engine, you must complete your domain whitelisting and sender authentication protocols straight inside your external SendGrid console interface rather than our account settings dashboard.

⚠️
SendGrid Regional Routing Restrictions
Due to strict international delivery policies and compliance constraints, SendGrid may automatically block or reject outbound mail streams targeted at specific consumer country-code top-level domains (ccTLDs). Messaging payloads destined for email addresses ending in .ir (Iran), .sy (Syria), or .cu (Cuba) will face hard blocking parameters at the server layer and will fail to arrive at their destinations.
Was this article helpful?
Related articles
πŸ“„ How to generate a SendGrid API key and add it to SystemeScale β†’ πŸ“„ How to authenticate your domain name for email sending β†’ πŸ“„ Is it possible to integrate SystemeScale with an external autoresponder? β†’