Articles on: Senders

Send Newsletters with SendGrid

Send Newsletters with SendGrid


Who this is for


Teams that want to send HTML newsletters or broadcast emails through SuperSend using their own SendGrid account as the sending infrastructure. This setup gives you full control over your sending reputation, lets you use custom HTML email templates, and keeps all campaign management inside SuperSend.


How it works


SendGrid is an API-based email provider. Instead of connecting a single Gmail or Outlook mailbox, you connect your entire SendGrid account via an API key. SuperSend uses that key to send email through SendGrid on your behalf. You then build your newsletter as a campaign in SuperSend — using an HTML template for the email body — and assign the SendGrid sender to it.


The full path is: SendGrid account → domain authenticated → API key created → connected to SuperSend as a sender → attached to a sender profile → used in a campaign.



Step 1: Create a SendGrid Account


  1. Go to sendgrid.com and click Start for Free (or log in if you already have an account).
  2. Fill in your name, email, and password. SendGrid will send a verification email — click the link to confirm your account.
  3. Complete SendGrid's onboarding questions (company name, sending volume, use case). These help SendGrid assign the right sending tier to your account.


Which plan do you need? The free plan allows up to 100 emails/day. For newsletter volumes (thousands of recipients), you'll need a paid Essentials or Pro plan. Choose based on your monthly send volume.



Step 2: Authenticate Your Sending Domain in SendGrid


Domain authentication tells receiving mail servers that SendGrid is allowed to send on behalf of your domain. This is required for good deliverability — unauthenticated sending will result in spam placement or rejected messages.


  1. In the SendGrid dashboard, go to SettingsSender Authentication.
  2. Under Domain Authentication, click Authenticate Your Domain.
  3. Select your DNS host (e.g., Cloudflare, GoDaddy, Route 53) and enter your sending domain (e.g., yourcompany.com).
  4. SendGrid generates a set of CNAME records. Add each of these records to your domain's DNS settings with your DNS provider.
  5. Return to SendGrid and click Verify. It can take up to 48 hours for DNS changes to propagate, but usually resolves within a few minutes to a few hours.


Once domain authentication shows a green checkmark, your domain is ready for sending.


Note: If you don't want to set up full domain authentication right away, you can use a verified single sender (Settings → Sender Authentication → Single Sender Verification) as a starting point. However, domain authentication is strongly recommended for any newsletter-scale sending.



Step 3: Create a SendGrid API Key


  1. In SendGrid, go to SettingsAPI Keys.
  2. Click Create API Key.
  3. Give it a descriptive name, e.g., SuperSend Newsletter.
  4. Under API Key Permissions, select Restricted Access.
  5. Scroll to Mail Send and set it to Full Access. No other permissions are required for sending through SuperSend.
  6. Click Create & View.
  7. Copy the API key immediately. SendGrid only shows the full key once. If you lose it, you'll need to generate a new one.



Step 4: Add SendGrid as a Sender in SuperSend


  1. In SuperSend, go to Senders in the left sidebar.
  2. Click Add SenderEmail Sender.
  3. On the method selection screen, click Connect Your Own Mailboxes.
  4. From the provider list, select SendGrid.
  5. Enter the following:


Field

What to enter

API Key

The key you copied from SendGrid in Step 3

Send As Email

The email address you're sending from (e.g., news@yourcompany.com). This must match the domain you authenticated in Step 2.

Reply-To Email

Where replies should go (can be the same address or a separate inbox).


  1. Click Connect.


SuperSend verifies the API key and registers the sender. It appears in SendersMailboxes with an active status.



Step 5: Create a Sender Profile for Your Newsletter Sender


Sender profiles are what campaigns actually use — campaigns connect to profiles, not individual mailboxes directly.


  1. Go to SendersSender Profiles tab.
  2. Click Create Profile (or open an existing profile if you want to add the SendGrid sender to it).
  3. Give the profile a clear name, e.g., Newsletter — yourcompany.com.
  4. Click Add Mailboxes and select the SendGrid sender you just connected.
  5. Save the profile.



Step 6: Build a Newsletter Campaign in SuperSend


  1. In the left sidebar, go to your team and click Campaigns.
  2. Click New Campaign and give it a name.
  3. When setting up the campaign sequence, add an Email step.
  4. In the email step editor, switch to HTML mode (look for the HTML toggle or source editor button in the toolbar). Paste or build your HTML newsletter template here.
  5. In campaign SettingsSenders, assign the sender profile you created in Step 5.
  6. Configure the rest of your campaign settings (schedule, sending hours, etc.) as needed.
  7. Upload or add your contacts, then launch the campaign.



Sending Your Next Newsletter (Same Campaign, New Issue)


Once your first newsletter has sent, the simplest way to send a second issue to the same list is to reuse the same campaign rather than create a new one. Here's how:


  1. Open the campaign and go to the Sequence tab.
  2. Click into the email step and replace the HTML content with your new newsletter issue. Save the step.
  3. Go to the Contacts tab of the campaign.
  4. Click the checkbox at the top of the contacts table to select all contacts.
  5. With all contacts selected, click Restart.
  6. Confirm the restart. SuperSend resets the selected contacts back to a fresh state, as if they're entering the campaign for the first time.
  7. Start (or resume) the campaign. SuperSend will send the updated email to all restarted contacts.


Why this works: Restarting contacts clears their completed status so they'll be processed again by the sequence — this time picking up the new template you saved in step 2.


Things to keep in mind:

  • Update the email template before restarting contacts. If you restart first and then edit, contacts may start sending before your new content is saved.
  • Any contacts added after the first send will also be included when you restart, so review your list if you don't want new additions in the next issue.
  • This pattern works for as many newsletter issues as you want to send — just repeat: update template → select all → restart → send.



What to expect


  • Emails are sent via SendGrid's API. Delivery events (sent, opened, clicked, bounced) are tracked within SuperSend's campaign analytics.
  • Because SendGrid is an API sender, reply tracking through IMAP is not available by default. Replies go to whatever address you set as the Reply-To in Step 4. If you need replies to appear in SuperSend's Super Inbox, you would need to configure inbound parsing at your email provider and connect a separate IMAP mailbox as the reply destination.
  • Sending limits are determined by your SendGrid plan, not by SuperSend.
  • HTML templates render as-is. Test your template with a small send before launching to your full list.



Troubleshooting


Issue: The API key fails when connecting in SuperSend.

Fix: Double-check that you copied the full key (it starts with SG.). Also confirm the key has Mail Send → Full Access permissions in SendGrid. Keys scoped to read-only or other permissions won't work.


Issue: Emails go to spam.

Fix: Ensure domain authentication is fully verified in SendGrid (green checkmark). Also confirm the Send As Email matches the authenticated domain. Unauthenticated or mismatched sender domains are the most common cause of spam placement.


Issue: The Send As Email is rejected.

Fix: The email address used must belong to the domain you've authenticated (or be a verified single sender). Using an address from a different domain will cause SendGrid to reject sends.


Issue: Replies don't appear in SuperSend.

Fix: API senders don't support IMAP-based reply monitoring. To track replies, configure your reply-to inbox with a forwarding rule or use a separate IMAP-connected mailbox as the reply-to address.





Updated on: 26/03/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!