Something happens on your WordPress site, and a new contact appears on your SendGrid list. The record maps straight across the instant the event fires — a direct, real-time connection built into WordPress itself, no extra plugin required.
What a WordPress Core → SendGrid connection can do
When this happens in WordPress Core
What happens in SendGrid
The one thing this connection does in SendGrid
Everything you need to know about the WordPress Core & SendGrid integration
No. Install Integrazo Automator, authorise SendGrid once, pick the WordPress event as the trigger, map the post, user and comment fields to SendGrid custom fields and switch the connection on. There is no webhook URL to paste and no JSON to write.
The one you pick when you build the connection. Every contact it adds goes to that list, with the fields you mapped.
Yes. Every one of your post, user and comment fields is offered against every standard and custom field on your SendGrid account — pick the ones you want mapped.
No — SendGrid matches contacts by email address, so a repeat submission updates the existing contact rather than creating a second one.
Yes. Add a filter condition on any mapped field — contains, equals, starts with, is empty and the rest, combined with AND/OR — and only entries matching it are sent to SendGrid. Everything else is skipped and still shows up in your Logs.
The run is logged as failed with the error Twilio SendGrid returned, and the event is still saved in WordPress — nothing is lost. Once the problem is fixed, the next matching event goes through as normal.
No. The connection runs on your own WordPress site and talks to SendGrid directly. The OAuth token is encrypted in your database, and there is no middleman service holding a copy of your data.
The core plugin is free on WordPress.org and covers a single connection. Pro adds unlimited connections, multiple lists per connection, and custom field mapping, and priority support.