Newsletter Signup + SendGrid
Capture email signups, add to SendGrid contact list, and send a welcome email with a lead magnet attachment.
Replaces
Zapier ($20/mo) + ConvertKit ($29/mo)
Savings
$588/year
What This Workflow Does
Captures Signups
Receives email addresses from your website form via webhook.
Adds to SendGrid
Automatically adds the contact to your SendGrid marketing list.
Sends Welcome Email
Triggers a personalized welcome email using SendGrid dynamic templates.
Delivers Lead Magnet
Attaches your lead magnet (PDF, ebook, etc.) to the welcome email.
How to Set Up Newsletter Signup Automation
Complete step-by-step guide to setting up this n8n workflow for automated newsletter signups with SendGrid integration
- 1
Import the Workflow
Download the JSON file below and import it into your n8n instance. In n8n, go to Settings → Import from File and select the downloaded JSON. The workflow will appear in your workflows list.Learn more → - 2
Configure SendGrid Credentials
Click on any SendGrid node in the workflow and add your SendGrid API key in the credentials panel. You can create an API key in your SendGrid dashboard under Settings → API Keys. Give it 'Full Access' permissions.Learn more → - 3
Set Your SendGrid List ID
Update the 'Add Contact to List' node with your SendGrid contact list ID. Find this in SendGrid under Marketing → Contacts. Copy the list ID and paste it into the workflow node configuration.Learn more → - 4
Connect Your Website Form
Activate the workflow and copy the webhook URL from the Webhook node (it will look likehttps://your-n8n.com/webhook/newsletter-signup). Update your website form to POST to this URL with the email field. - 5
Test & Activate
Test the workflow by submitting a test email through your form. Check SendGrid to verify the contact was added and the welcome email was sent. Once confirmed, your workflow is live and will run automatically for all new signups.
Ready to Download?
This workflow is completely free. No email required, no strings attached.
Need help setting this up? Contact me
Created by

n8n automation expert and founder of this community. Helping entrepreneurs escape the subscription trap with self-hosted automation.
Requirements
- n8n instance - Self-hosted or cloud (DashNex recommended)
- SendGrid account - Free tier works (up to 100 emails/day)
- SendGrid API key - With Marketing permissions
- SendGrid contact list - Create one in your SendGrid dashboard
- Website form - Any HTML form that can POST to a webhook
Approaches I Rejected
These alternatives look simpler but create problems down the line
Direct webhook to SendGrid
Why it seems better: One node, no n8n in the middle, fewer moving parts.
Why I rejected it: No error handling. No retry logic. No validation. When SendGrid has a 30-second outage (they all do), you silently lose signups. The user sees "success" but nothing happens. You don't find out until someone emails you asking why they never got the PDF.
ConvertKit/Mailchimp native forms
Why it seems better: No code. Drop in an embed and you're done.
Why I rejected it: You're locked into their form styling. You can't add custom validation. You can't branch logic based on answers. You can't A/B test without paying for their expensive tier. And most critically: you have no visibility into failures. The form just... stops working sometimes, and you only know when leads dry up.
Zapier multi-step zap
Why it seems better: More visual, "no code," everyone's heard of it.
Why I rejected it: $20/month minimum for this simple flow. Task limits that reset monthly. No real error visibility—just "zap failed" in an email you'll miss. Can't self-host. Can't customize beyond what they expose. This workflow costs $0/month in n8n self-hosted and gives you full control.
Storing emails in a Google Sheet first
Why it seems better: "Backup" in case SendGrid fails. Human-readable list.
Why I rejected it: Creates a sync nightmare. Now you have two sources of truth. The Sheet gets out of sync with SendGrid. Someone manually adds an email to the Sheet but not SendGrid. Someone unsubscribes in SendGrid but you keep emailing them from the Sheet export. If you need a backup, SendGrid already has one—it's called their contact list export.
What Breaks When
Every workflow fails eventually. Here's how this one degrades and what to do about it.
SendGrid API is down
Symptom: Webhook responds 200 but no email arrives. Contact not added to list.
Detection: The workflow logs a failed execution in n8n. You can set up a webhook to Slack/Discord when executions fail.
Recovery: Built-in retry (3 attempts with exponential backoff). If all retries fail, the execution stays in "error" state so you can manually re-run it when SendGrid is back.
Invalid email submitted
Symptom: SendGrid rejects the contact. No welcome email sent.
Detection: The "Add Contact" node fails with a 400 error. Logged in n8n execution history.
Recovery: Add email validation in your frontend form before submission. The workflow includes a basic format check, but disposable email domains (mailinator, etc.) will still get through. Consider adding a blocklist node if spam becomes a problem.
SendGrid rate limit hit
Symptom: First N emails work, then you get 429 errors.
Detection: Execution fails with "Too Many Requests" error.
Recovery: This only happens if you're adding contacts extremely fast (unlikely for organic signups). If you're bulk-importing, add a 1-second delay between items. SendGrid free tier allows 100 emails/day—consider upgrading if you're hitting limits.
n8n instance is down
Symptom: Webhook returns 502/503. Form submission fails visibly to the user.
Detection: User sees an error. Your uptime monitor (BetterUptime, UptimeRobot) alerts you.
Recovery: You've lost that signup—there's no queue. Fix your n8n instance. If downtime is a concern, run n8n behind a load balancer with a second instance, or use n8n Cloud which handles this for you.
Duplicate email submitted
Symptom: Same person signs up twice.
Detection: SendGrid silently deduplicates—no error thrown.
Recovery: No action needed. SendGrid won't add duplicates to your list or send duplicate welcome emails. The workflow is idempotent by design.
Pro tip: Set up execution monitoring in n8n. Go to Settings → Workflows → Error Workflow and point it at a workflow that posts to Slack, Discord, or email. You'll know within minutes when something breaks—not days later when a customer complains.