SendGrid Integrations: Native, Zapier, and API

SendGrid publishes no WordPress plugin of its own, so use a mailer plugin. WP Mail SMTP and Easy WP SMTP both ship a SendGrid mailer routing wp_mail() through the Web API with an API key — preferable on shared hosting, where outbound SMTP ports are often blocked. For SMTP instead: smtp.sendgrid.net, port 587, username apikey, API key as the password — see the SMTP settings tab. Authenticate your domain first, or notifications send unaligned.

Not through a SendGrid-built app: Twilio SendGrid publishes neither a Shopify app nor a WooCommerce extension. WooCommerce inherits whatever WordPress uses, so a mailer plugin covers every order email. Shopify needs Zapier, a private app calling POST /v3/mail/send, or middleware such as Make. If a native e-commerce connector is a hard requirement, Brevo maintains one.

Both authenticate with an API key, and both are partner-built. Zapier exposes Send Email, Create or Update Contact and Find List by Name, plus a beta API Request action reaching any v3 endpoint it has not wrapped; Make covers sending plus contacts, lists and suppressions. Give each its own scoped key with Mail Send permission only — a leaked automation credential should not read your contact database.

Segment is the one CDP with a first-party path both ways: the destination writes identify and track events into contacts, the source streams email events back. Twilio owns Segment, which is why this connector exists and no other CDP connector does. mParticle forwards audiences from its own side. Anything else uses PUT /v3/marketing/contacts, which upserts asynchronously and returns a job_id you poll — build for that, not a synchronous write.

Two of the three have a maintained transport. Symfony has the official symfony/sendgrid-mailer bridge, driven by a sendgrid:// DSN over API or SMTP. Django has Anymail, whose backend also handles inbound and tracking webhooks. Laravel has no SendGrid-specific transport here — use its built-in smtp mailer against smtp.sendgrid.net on port 587 with username apikey, or the official PHP SDK (composer require sendgrid/sendgrid).

All three have first-party listings; the difference is billing, not capability. The Heroku add-on provisions an account and injects config vars into the dyno, with plans from Essentials 50K to Premier 20M. The AWS and Azure listings create a real account billed on the cloud invoice, which is how enterprises route email into committed spend. On Compute Engine, Google publishes its own relay tutorial because GCE blocks outbound port 25 — use 587 or 2525. EU caveat: regional EU sending needs an EU Data Resident subuser, an EU dedicated IP and the api.eu.sendgrid.com base URL together, on Pro or above.