Something happens on your WordPress site, and a new event appears on your Google Calendar. 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 → Google Calendar connection can do
When this happens in WordPress Core
What happens in Google Calendar
The one thing this connection does in Google Calendar
Everything you need to know about the WordPress Core & Google Calendar integration
No. Install Integrazo Automator, authorise Google Calendar once, pick the WordPress event as the trigger, map the post, user and comment fields into the event details 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. Title, time and description come from the fields you mapped.
Yes. Build the title and description from any of your post, user and comment fields plus fixed text of your own, and set the guest list to include the submitter if you want.
Yes — each run creates a new event; Google Calendar doesn't dedupe events. Pair the connection with your form plugin's own duplicate-submission protection if that matters.
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 Google Calendar. Everything else is skipped and still shows up in your Logs.
The run is logged as failed with the error Google 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 Google Calendar 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 calendars per connection, and automatic guest invites, and priority support.