SendGrid

Use SendGrid when you want Drip Drop to send email through a dedicated email delivery platform instead of a personal mailbox. SendGrid can handle outbound sending, event webhooks, engagement tracking, and inbound parse for replies.

Note
SendGrid is different from Gmail and Outlook. It is an email service provider for application sending, not a mailbox login flow.
  • You want high-volume or application-style email sending rather than sending from a mailbox account.
  • You want provider-side delivery, bounce, open, click, unsubscribe, and related webhook events in Drip Drop.
  • You want reply handling through a dedicated inbound parse domain instead of an inbox subscription or IMAP mailbox connection.
  • Confirm you have SendGrid account access and permission to create API keys and edit webhook settings.
  • Verify at least one sender identity or authenticate its domain in SendGrid.
  • For replies, prepare a dedicated hostname and point its MX record to SendGrid before enabling Inbound Parse.
    Note
    Create or choose a safe test contact before turning the provider loose on production traffic.
Choose SendGrid from the New Integration provider list.
  1. Open Integrations → Email.
  2. Click New Integration and choose SendGrid.
Name the SendGrid integration and enter its API key and optional IP pool.
  1. On Connect, enter a Name and API Key. Enter IP Pool only if that pool already exists in SendGrid.
Review the SendGrid webhook status, verification controls, tracking options, inbound parsing, and signed-webhook settings. The generated webhook URL is hidden for documentation.
  1. On Webhooks, configure the optional webhook settings or skip them and finish setup later from the integration settings.
Review the verified sender address available to the SendGrid integration.
  1. On Senders, sync sender identities from SendGrid or add an email address manually, then continue.
Confirm that credentials, webhook configuration, and a sender are present before finishing setup.
  1. On Verify, review Credentials stored, Webhook, and Senders, then finish the wizard.

Credentials stored confirms that a key is saved. SendGrid does not provide a separate live credential check in this wizard; the key is exercised when Drip Drop syncs senders, configures webhooks, or sends email.

The current SendGrid integration expects different API permissions depending on what you enable.

Mail Send: Full Access for outbound email. Sender Verification: Read Access to import sender identities.
Event Webhooks: Read access for verification and full access if Drip Drop should auto-configure the event webhook.
Inbound Parse: Full access if Drip Drop should configure or update inbound parse settings.

SendGrid references: API key permissions.

  • On Senders, select Sync from provider to import sender identities from SendGrid, or add an email address manually.
  • Verified means SendGrid verified that address or authenticated its domain. Unverified means SendGrid does not list it as verified, so sending may fail. A sender with unknown status has no badge.
  • Set the sender a flow should use. Outbound sending can work without Event Webhook or Inbound Parse.

The Event Webhook sends delivery and engagement events to Drip Drop. It is separate from Inbound Parse.

  • Choose Track Opens and Track Clicks before selecting Configure Webhook. Drip Drop saves the current options, then creates or updates the SendGrid endpoint.
  • Select Verify Webhook to check the stored endpoint and exact URL. A successful check shows Webhook configured and Last verified.
  • For a manually created endpoint, verification remains manual until Drip Drop receives an accepted event.
  • If automatic configuration fails, copy the displayed webhook URL into SendGrid Event Webhook settings.

Track Opens and Track Clicks add SendGrid engagement events to the Event Webhook. Drip Drop Tracking is a separate, mutually exclusive tracking method.

  • After changing Track Opens, select Configure Webhook again so the SendGrid endpoint uses the new event selection.
  • After changing Track Clicks, select Configure Webhook again so the SendGrid endpoint uses the new event selection.
  • Use either SendGrid tracking or Drip Drop Tracking; enabling one turns the other off.

SendGrid supports signed Event Webhooks. When enabled, Drip Drop uses SendGrid’s ECDSA public verification key to validate requests.

  • Enable Signed Webhooks before selecting Configure Webhook so Drip Drop enables SendGrid signing and saves the public key.
  • For manual signed setup, paste the SendGrid public key into Webhook Verification Key. Missing or invalid signatures are rejected while signing is enabled.
  • Send a test event after saving the key and confirm Last verified updates after Drip Drop accepts it.

Inbound Parse routes incoming email through a dedicated hostname. It is separate from the Event Webhook.

  • Enable Inbound Parse and enter the Inbound Parse Domain.
  • Point the hostname’s MX record to SendGrid, then select Configure Webhook to create or update the parse setting.
  • If automatic setup fails, configure the hostname and displayed destination URL in SendGrid.
  • A valid In-Reply-To tracking ID from the intended contact records a reply. A sender-only fallback can thread the message but does not count as a reply or branch a flow.
  1. Open SendGrid Event Webhook settings if Drip Drop cannot auto-configure the event webhook.
  2. Enable the event types Drip Drop needs, including Opens and Clicks if you want engagement events.
  3. If signed webhooks are required, enable Signed Delivery and keep the verification key available to Drip Drop.
  4. Open SendGrid Inbound Parse settings if you need reply handling.
  5. Configure the Parse Hostname, Destination URL, and any required DNS or MX records for that hostname.

Helpful SendGrid references: Event Webhook docs, Signed Event Webhook docs, and Inbound Parse docs.

  • After webhook traffic starts arriving, Drip Drop can attach delivery and engagement events to outbound messages.
  • Verification State may depend on whether the webhook was auto-configured or manually created.
  • Inbound replies can appear even though they come through the parse domain rather than the normal event webhook.
API key and permissions
  • If sender import fails, grant Sender Verification Read Access. If webhook inspection fails, grant Event Webhooks Read Access; automatic configuration requires Full Access.
  • If sending fails, confirm Mail Send has Full Access, the API key has not been revoked, and the selected sender is verified in SendGrid.
Webhook and verification problems
  • If Verify Webhook reports a mismatch, compare the exact URL in SendGrid with the URL shown in Drip Drop.
  • If signed events are rejected, confirm Signed Webhooks is enabled and Webhook Verification Key is saved. Configure again to retrieve a new public key when needed.
  • A manually created endpoint cannot be verified by stored endpoint ID. Send a test event and confirm Last verified updates after Drip Drop accepts it.
Tracking problems
  • If opens are missing, enable Track Opens and select Configure Webhook again. Confirm Drip Drop Tracking has not replaced provider tracking.
  • If clicks are missing, enable Track Clicks, configure again, and confirm the message contains a trackable link.
Inbound parse problems
  • If replies do not arrive, confirm the Inbound Parse Domain matches SendGrid and its MX record points to SendGrid.
  • If automatic setup fails, grant Inbound Parse Full Access or configure the hostname and destination URL manually in SendGrid.
  • If a message is threaded but no reply action runs, send a fresh message and reply to it. Only a valid In-Reply-To tracking ID from the intended contact creates a reply event; automatic replies do not.
  • See Integrations for the shared provider setup flow and provider management basics.
  • Compare Gmail or Outlook if you need a mailbox-style email sender instead of an ESP.