1. What area of SendGrid do you need help with?
   • A) Email API — sending transactional email via REST API or SMTP relay, SDKs
   • B) Marketing Campaigns — drag-and-drop editor, single sends, automations, signup forms
   • C) Dynamic Templates — Handlebars-based transactional templates, template versioning
   • D) Domain Authentication — SPF/DKIM/DMARC setup, branded tracking links, reverse DNS
   • E) Event Webhooks — delivery events, engagement events, webhook configuration
   • F) Inbound Parse — receiving and parsing inbound email via webhook
   • G) Email Validation API — address validation, disposable domain detection
   • H) Dedicated IPs / Deliverability — IP warmup, IP pools, sender reputation
   • I) Suppressions — bounces, blocks, spam reports, unsubscribe management
   • J) Analytics / Statistics — aggregate stats, category stats, mailbox-provider stats
   • K) Account / Billing — plans, pricing, subusers, teammates, API keys
   • L) Something else — describe it
2. What's your role?
   • A) Developer / engineer
   • B) Marketing manager / email marketer
   • C) DevOps / infrastructure
   • D) Admin / account owner
   • E) Founder / solo operator
   • F) Agency / freelancer
   • G) Other
3. What are you trying to accomplish? (describe your specific goal or question)

• General email marketing strategy / best practices ->

  /sales-email-marketing

• Cross-platform email deliverability (not SendGrid-specific) ->

  /sales-deliverability

• Email open/click tracking strategy ->

  /sales-email-tracking

• Connecting SendGrid to other tools via Zapier or middleware ->

  /sales-integration

• Funnel strategy / conversion optimization ->

  /sales-funnel

• REST API:

  POST /v3/mail/send

  — send transactional email with full control over headers, content, attachments, tracking, and scheduling
• SMTP relay: Connect any SMTP-capable application to

  smtp.sendgrid.net

  (port 587 TLS or 465 SSL) using an API key as the password
• SDKs: Official libraries for Node.js (

  @sendgrid/mail

  ), Python (

  sendgrid

  ), PHP, Java, C#, Go, Ruby
• Personalizations: Send to multiple recipients with per-recipient substitutions, headers, and categories in a single API call (up to 1,000 personalizations per request)
• Scheduling: Schedule emails up to 72 hours in advance via the

  send_at

  parameter (Unix timestamp)
• Attachments: Up to 20MB total message size including attachments
• Categories: Tag emails with up to 10 categories for filtering in statistics
• Rate limits: General API 600 req/min; mail/send endpoint supports up to 10,000 req/sec on high-volume plans

• Single Sends: One-time email broadcasts to a list or segment — drag-and-drop editor or code editor
• Automations: Trigger-based multi-step email sequences — welcome series, date-based, custom triggers
• Signup Forms: Embedded or hosted forms to capture contacts and add them to lists
• Segmentation: Filter contacts by engagement, demographics, custom fields, list membership — AND/OR logic
• A/B Testing: Test subject line, content, or sender on single sends — winner selected by open rate or click rate after configurable test duration
• Email Testing: Inbox rendering across email clients, link validation, spam testing (credit-based)
• Design Library: Reusable content modules and templates shared across single sends and automations
• Key distinction: Marketing Campaigns is a separate subscription from the Email API — you may need both if you send transactional and marketing email

• Handlebars syntax: Use

  {{variable}}

  ,

  {{#if}}

  ,

  {{#each}}

  ,

  {{#unless}}

  for dynamic content in transactional templates
• Template versioning: Multiple versions per template — set an active version, test new versions before activating
• Template editor: Visual editor or code editor in the SendGrid UI
• API usage: Pass

  template_id

  and

  dynamic_template_data

  in the mail/send request to render a template with dynamic data
• Test data: Preview templates with test data in the UI before sending

• SPF/DKIM: Automated DNS record generation — add CNAME records to your DNS provider to authenticate your sending domain
• DMARC: SendGrid provides guidance but DMARC records must be configured directly in your DNS
• Branded tracking links: Replace default SendGrid tracking URLs with your own domain (e.g.,

  links.yourdomain.com

  )
• Reverse DNS (rDNS): Map a SendGrid IP to your domain for improved deliverability — required for dedicated IPs
• Link branding: Custom domain for click tracking and open tracking pixels
• Automated security: SendGrid rotates DKIM keys automatically when using automated security (default)

• Included on: Pro+ plan (Email API) and Advanced+ plan (Marketing Campaigns)
• IP warmup: Automated warmup mode gradually increases sending volume over the IP — recommended for new IPs
• Manual warmup: Create your own warmup schedule for finer control over volume ramp-up
• IP pools: Group multiple IPs into pools and assign them to different mail streams (transactional vs. marketing, by category, etc.)
• IP access management: Restrict API access to specific IP addresses for security

• Delivery events: processed, dropped, delivered, deferred, bounce
• Engagement events: open, click, spam report, unsubscribe, group unsubscribe, group resubscribe
• Configuration: Set a webhook URL in Settings > Mail Settings > Event Webhook — select which events to receive
• Payload: JSON array of event objects with email, timestamp, event type, and metadata (categories, custom args)
• Signed webhooks: Verify webhook authenticity using the Event Webhook signature verification (OAuth public key)
• Retry logic: SendGrid retries failed webhook deliveries for up to 24 hours

• What it is: Receive inbound email at your domain and have SendGrid parse it into structured data (from, to, subject, body, attachments) sent to your webhook URL
• Setup: Add an MX record pointing your domain to

  mx.sendgrid.net

  , then configure the Inbound Parse webhook URL in the SendGrid UI
• Raw vs. parsed: Choose between receiving raw MIME or pre-parsed fields (JSON)
• Attachments: Attachments are included as multipart form data in the webhook POST
• Use cases: Support ticket creation, lead capture from email replies, email-to-app workflows

• Real-time validation: Check email addresses at point of capture for deliverability risk
• Checks performed: Syntax validation, MX record lookup, disposable domain detection, known-invalid detection, typo correction suggestions
• Plan requirement: Pro+ plan (Email API) — included 2,500 validations/month on Pro, additional validations available
• Bulk validation: Upload a CSV of email addresses for batch validation
• API endpoint:

  POST /v3/validations/email

• Automatic management: SendGrid automatically manages bounces, blocks, spam reports, and unsubscribes
• Bounce list: Hard bounces are automatically added — future sends to these addresses are dropped
• Block list: Temporary delivery failures (server rejections) — can be retried after resolving the issue
• Spam report list: Addresses that marked your email as spam — automatically suppressed from future sends
• Unsubscribe management: Global unsubscribes and group unsubscribes (suppression groups)
• Suppression groups: Create categories of email (e.g., "Marketing", "Product Updates", "Billing") and let recipients unsubscribe from specific groups rather than all email
• API access: Full CRUD access to all suppression lists via the API

• Aggregate stats: Overall account-level delivery and engagement metrics
• Category stats: Filter stats by categories assigned to emails
• Mailbox provider stats: See delivery and engagement broken down by receiving provider (Gmail, Yahoo, Outlook, etc.)
• Browser/device stats: See which browsers and devices recipients use to open emails
• Geographic stats: Open and click activity by geographic location
• Subuser stats: Per-subuser statistics for accounts with multiple subusers

• Base URL:

  https://api.sendgrid.com/v3/

• Authentication: Bearer token —

  Authorization: Bearer <API_KEY>

• Rate limits: 600 req/min general; mail/send up to 10,000 req/sec on high-volume plans
• Message size: 20MB maximum (including attachments)
• Personalizations: Up to 1,000 per mail/send request
• Key endpoints:

  • POST /v3/mail/send

    — send email

  • GET /v3/stats

    — aggregate statistics

  • GET /v3/suppression/bounces

    — list bounced addresses

  • GET /v3/templates

    — list templates

  • PUT /v3/marketing/contacts

    — add/update marketing contacts

  • POST /v3/marketing/singlesends

    — create single send

  • POST /v3/validations/email

    — validate email address
• SDKs: Node.js (

  @sendgrid/mail

  ,

  @sendgrid/client

  ), Python, PHP, Java, C#, Go, Ruby
• Docs: docs.sendgrid.com

1. Sending transactional email via the API:
   1. Create an API key in Settings > API Keys with "Mail Send" permission
   2. Authenticate your sending domain in Settings > Sender Authentication (add the CNAME records to your DNS)
   3. Install the SDK for your language (e.g.,

      npm install @sendgrid/mail

      for Node.js)
   4. Set the API key:

      sgMail.setApiKey(process.env.SENDGRID_API_KEY)

   5. Compose and send: set

      to

      ,

      from

      ,

      subject

      ,

      text

      /

      html

      (or

      templateId

      +

      dynamicTemplateData

      )
   6. Handle the response — check for 202 Accepted (success) or error codes
   7. Set up Event Webhooks to track delivery and engagement events
2. Setting up Marketing Campaigns automation:
   1. Subscribe to a Marketing Campaigns plan (automations require Advanced plan)
   2. Import or add contacts to a list — use CSV upload, signup forms, or the Contacts API
   3. Navigate to Automations > Create Automation
   4. Choose a trigger: welcome series (new contact added to list), date-based, or custom
   5. Build the email sequence — add email steps with delays between them
   6. Design each email using the drag-and-drop editor or code editor
   7. Activate the automation and monitor entry/completion rates in the automation dashboard
3. Configuring domain authentication:
   1. Go to Settings > Sender Authentication > Authenticate Your Domain
   2. Select your DNS host and enter your sending domain
   3. SendGrid generates CNAME records for SPF and DKIM — add these to your DNS provider
   4. Click Verify in SendGrid — it checks for the DNS records
   5. Set up branded tracking links (link branding) — add another CNAME for click/open tracking
   6. If using a dedicated IP, configure reverse DNS to map the IP to your domain
   7. Set up a DMARC record separately in your DNS (e.g.,

      v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com

      )
4. Setting up Event Webhooks:
   1. Go to Settings > Mail Settings > Event Webhook
   2. Enter your webhook URL (must be publicly accessible HTTPS endpoint)
   3. Select the events you want to receive (processed, delivered, open, click, bounce, etc.)
   4. Enable the webhook
   5. Implement signature verification on your endpoint using SendGrid's public key
   6. Process incoming JSON arrays of event objects — each has

      event

      ,

      email

      ,

      timestamp

      , and custom args
   7. Handle retries — SendGrid retries failed deliveries for up to 24 hours
5. Setting up Inbound Parse:
   1. Add an MX record for your receiving domain pointing to

      mx.sendgrid.net

   2. Go to Settings > Inbound Parse > Add Host & URL
   3. Enter your receiving domain and the webhook URL to receive parsed email
   4. Choose raw (MIME) or parsed (structured fields) format
   5. Implement your webhook endpoint to process the multipart POST data (from, to, subject, body, attachments)
   6. Test by sending an email to any address at your configured domain

Best-effort from research — verify details against current SendGrid documentation.

1. Email API and Marketing Campaigns are separate subscriptions with separate billing. Many users expect one plan covers everything. If you need to send both transactional email (order confirmations, password resets) and marketing email (newsletters, promotions), you need two subscriptions. Budget accordingly and understand which features belong to which plan.
2. The Free Trial is 60 days only with 100 emails/day — not a permanent free tier. Unlike some competitors, SendGrid's free offering expires. After 60 days you must upgrade to a paid plan or lose sending capability. Plan your evaluation and migration timeline around this limit.
3. Dedicated IPs require warmup or you will hit deliverability problems immediately. New dedicated IPs have no sending reputation. If you send high volume on a cold IP, mailbox providers will throttle or reject your email. Use SendGrid's automated warmup (enabled by default) or create a manual warmup schedule ramping from hundreds to your target volume over 4-6 weeks.
4. Suppression groups are not enabled by default — without them, unsubscribes are global. If you do not configure suppression groups (also called "unsubscribe groups"), any unsubscribe removes the contact from ALL your email. Set up suppression groups early (e.g., "Marketing", "Product Updates", "Billing Alerts") so recipients can opt out of specific categories without losing all communication.
5. Event Webhook payloads are batched and can be delayed — do not rely on them for real-time logic. SendGrid batches webhook events and may deliver them with a delay of seconds to minutes. If you need real-time delivery confirmation, poll the API or use the mail/send response code (202 = accepted for processing). Design your webhook consumers to handle out-of-order and duplicate events idempotently.

• /sales-email-marketing

  — Email marketing strategy and best practices (platform-agnostic)

• /sales-deliverability

  — Cross-platform email deliverability — SPF/DKIM/DMARC, warmup, inbox placement

• /sales-email-tracking

  — Email open and click tracking strategy

• /sales-integration

  — Connect SendGrid to other tools via Zapier, Make, or API

• /sales-funnel

  — Funnel strategy and conversion optimization

• /sales-do

  — Not sure which skill to use? The router matches any sales objective to the right skill. Install:

  npx skills add sales-skills/sales --skills sales-do

1. Walks through creating a restricted API key with only "Mail Send" permission for security
2. Guides domain authentication setup — adding CNAME records for SPF/DKIM
3. Shows how to install

   @sendgrid/mail

   and configure the API key via environment variable
4. Creates two Dynamic Templates in the SendGrid UI — one for password reset (with

   {{reset_link}}

   ) and one for welcome (with

   {{first_name}}

   ,

   {{login_url}}

   )
5. Provides code examples using

   sgMail.send()

   with

   templateId

   and

   dynamicTemplateData

6. Recommends setting up Event Webhooks to track delivery failures and trigger alerts for bounces Result: User has production-ready transactional email with templates, proper authentication, and delivery monitoring

1. Explains the dual-subscription model — Marketing Campaigns is separate from Email API, so they need the right plan (Basic or Advanced)
2. Walks through exporting contacts from Mailchimp (CSV) and importing into SendGrid with field mapping
3. Warns to only import subscribed contacts — recreate suppression groups in SendGrid before importing
4. Guides recreation of email templates using SendGrid's drag-and-drop editor or code editor
5. Covers DNS changes — remove Mailchimp's authentication records and add SendGrid's CNAME records for SPF/DKIM
6. Recommends a warmup strategy: start with most engaged contacts, gradually expand over 2-4 weeks, especially if using a new dedicated IP (Advanced plan) Result: User has a migration plan covering contacts, templates, DNS, suppressions, and warmup to maintain deliverability

1. Guides Event Webhook configuration — selecting processed, delivered, deferred, bounce, and dropped events
2. Walks through implementing a webhook endpoint that receives JSON event batches
3. Explains signature verification using SendGrid's public key to secure the endpoint
4. Designs the CRM update logic: mark contacts as "delivered" on delivery events, flag as "invalid" on hard bounces, queue for retry on deferrals
5. Warns about batched/delayed delivery and duplicate events — recommends idempotent processing using the event

   sg_message_id

   as a deduplication key
6. Suggests also subscribing to open and click events for engagement tracking in the CRM Result: User has a webhook pipeline that keeps their CRM in sync with SendGrid delivery and engagement events