Google Calendar Automations
Google Calendar Actions in Zapify: Setup and Every Action Explained
Bookings, consultations, classes and follow-ups all end up as something that needs a place in a calendar. Zapify PRO connects to Google Calendar and gives you five actions, so an event on your site — a form, a purchase, a sign-up — can put an event on a calendar and invite the right people without anyone typing it in twice. This page walks through the one-time Google setup, then explains each action and the things worth knowing before you build.
PRO feature
Google Calendar is a Zapify PRO integration and needs a Connection under Settings → Connections. It has no triggers in Zapify; use any trigger to start an automation and a Google Calendar action to react.
Set up the connection once
Google Calendar connects by signing in to a Google account, the same way Google Sheets does. Because Zapify runs on your own site, you create a small "OAuth client" in your own Google account first. This takes about ten minutes and is done once.
Part 1: Create the OAuth client in Google Cloud
- Open the Google Cloud Console and create a project, or pick one you already use for Zapify's Google Sheets connection.
- Go to APIs & Services → Library, search for Google Calendar API and click Enable. Skipping this is the most common reason a new connection fails its test.
- Go to APIs & Services → OAuth consent screen (called Google Auth Platform in newer accounts) and fill in the app name and your email. Choose Internal if you use Google Workspace and everyone who will connect is in your organisation; otherwise choose External.
- If you chose External and the app is in Testing, add the Google account you will connect under Test users.
- Go to APIs & Services → Credentials, click Create credentials → OAuth client ID and choose Web application.
- Under Authorised redirect URIs, add your site's callback address:
https://your-site.com/wp-admin/admin-post.php?action=zapify_oauth_callback
Replace your-site.com with your own domain. The Zapify screen in Part 2 shows the exact address to copy, so paste it from there if you are unsure.
- Click Create and keep the Client ID and Client secret that Google shows.
Testing mode expires after seven days
For an External app left in Testing, Google cancels the connection after seven days and you have to reconnect. To avoid this, go back to the consent screen and click Publish app. For your own use you can publish without Google's review; Google then shows an "unverified app" warning once when you connect, which you can continue past.
Part 2: Connect it in Zapify
- Go to Settings → Connections.
- Choose Google Calendar.
- Paste in the Client ID and Client secret from Google and save them. The screen also shows the redirect URI that Part 1 asked for.
- Click Connect, sign in with the Google account whose calendars you want to use, and approve access.
- Click Test. Zapify answers Connected to Google Calendar, with permission to read calendars and manage events. If Google says the Calendar API has not been used in the project, go back to step 2 of Part 1 and enable it.
Google Calendar and Google Sheets are separate connections, so each asks for the client ID and secret. You can paste in the same ones for both, as long as the redirect URI above is on the client. See Connections for how this screen works generally.
The actions
| Action | What it does | Main fields | Makes available afterwards |
|---|---|---|---|
| Create an event in Google Calendar | Adds an event, optionally with guests, reminders and a Google Meet link. | Calendar, Title, Start, End or Duration, Guests | Event ID, Event link, Google Meet link |
| Update an event in Google Calendar | Changes an event that already exists. Only the fields you fill in are changed. | Calendar, Event ID, and any event field | Event ID, Event link |
| Delete an event from Google Calendar | Removes an event. | Calendar, Event ID | — |
| Add a guest to a Google Calendar event | Invites one more person to an event. | Calendar, Event, Guest email | Event ID |
| Remove a guest from a Google Calendar event | Takes one person off an event's guest list. | Calendar, Event, Guest email | Event ID |
Every action also has a Connection field, which is where you pick the Google Calendar connection from above.
Fields on Create and Update
| Field | What it does |
|---|---|
| Calendar | The calendar to use. Only calendars this Google account can edit are listed. |
| Title | The event's name. |
| Description | Notes shown on the event. Plain text. |
| Location | An address or a place name. |
| All-day event | Makes it an all-day event, with no start or end time. |
| Start | When it begins, for example 2026-11-03 10:30. For an all-day event only the date is used. |
| End | When it ends. For an all-day event this is the last day, inclusive. |
| Duration (minutes) | Used when there is no End. Ignored if End is filled in. |
| Time zone | Defaults to your site's time zone, set under Settings → General in WordPress. |
| Guests | Email addresses separated by commas. |
| Email the guests | Whether Google emails guests about the change: Everyone, Only guests outside the organisation, or Nobody. |
| Add a Google Meet link | Creates a Meet link on the event. |
| Email reminder / Pop-up reminder | Minutes before the event. Leave empty to keep the calendar's own reminders. |
On Create, you need a Start and either an End or a Duration (an all-day event can leave both empty and lasts one day).
Things worth knowing
Start accepts the usual date formats. 2026-11-03 10:30 and 2026-11-03T10:30 both work and are read in the Time zone you chose. A value that already carries an offset, such as 2026-11-03T10:30:00+05:30, keeps it. If a form gives you a date and a time as two fields, put the two tokens side by side in Start with a space between them.
All-day events end on the last day you mean. Set Start to the 3rd and End to the 4th and you get a two-day event covering both days. You do not need to add one to the end date; Zapify does that for Google.
Guests get an email by default. Email the guests starts on Everyone, because the usual job is "book it and invite them". Change it to Nobody for events you only want on the calendar.
Update changes only what you fill in. Leave a field empty and the event keeps what it has, so you can reschedule by setting only Start. When you give a new Start but no End or Duration, the event keeps its current length. Filling in Guests replaces the whole guest list, so use Add a guest and Remove a guest to change one person.
Adding and removing guests is safe to run twice. If the person is already invited, Add a guest does nothing and reports success. If they are not on the event, Remove a guest does the same. Neither one touches the other guests.
Delete is forgiving about repeats. Deleting an event that Google says is already gone counts as success. An event that cannot be found at all is reported as a failure, because it usually means the wrong calendar or event ID.
Choose an event, or use a token. On Add a guest and Remove a guest, the Event field lists the next 50 upcoming events on the chosen calendar, which is handy for a fixed event such as a weekly class. It also accepts the Event ID token from a Create an event action earlier in the same automation. On Update and Delete, the Event ID field takes a token or an ID you type.
Failures say why. Google's own message appears in Zapify → Logs, such as Not Found or Invalid attendee email. A busy or briefly unavailable Google is reported as a temporary failure that can be retried; a problem with your data is reported straight away.
Ready-made guides
- Create a Google Calendar event from a Contact Form 7 booking form
- Add a follow-up to Google Calendar when a user registers
- Invite a customer to a Google Calendar event when a product is purchased
- Remove a customer from a Google Calendar event when an order is refunded
FAQs
Is this free in Zapify?
No. Google Calendar is part of Zapify PRO and needs an active licence and a Connection.
Do I need a Google Workspace account?
No. A free Google account works. Workspace only adds the Internal option on the consent screen.
Why does the Calendar dropdown only show some of my calendars?
It lists calendars the connected account can edit. Calendars shared with you as view-only are left out, because an event could never be added to them.
Why did my connection stop working after a week?
Your Google Cloud app is probably still in Testing. Publish it on the OAuth consent screen, then reconnect once. See the note under Set up the connection once.
Why does Google say "redirect_uri_mismatch"?
The address on your OAuth client does not match the one Zapify sends. Copy the redirect URI shown on the Google Calendar connection screen into Authorised redirect URIs in Google Cloud exactly as shown, including https and no trailing slash.
Can an automation start when an event is added to my calendar?
Not yet. Google Calendar has actions only. Use any other Zapify trigger to start the automation.
Do I need to write any code?
No. The Google setup is a few clicks in Google Cloud, and everything else is configured in the Zapify visual builder.