Optional. Without it, Card still takes bookings and emails you; it simply cannot see the rest of your diary, so it will offer times you are already busy.
With it, two things happen: times blocked in your Google Calendar disappear from the picker, and every booking appears in your calendar as a real event.
You will need a free Google Cloud account.
- Go to console.cloud.google.com and create a project. Name it anything.
- APIs & Services → Library → Google Calendar API → Enable.
- APIs & Services → OAuth consent screen. Choose External. Fill in an app name and your email. Save.
- Still on the consent screen, add yourself as a Test user. This is not optional: in testing mode Google refuses consent to anyone not listed, and the connection will fail with a warning screen.
- Credentials → Create credentials → OAuth client ID → Web application.
- Under Authorised redirect URIs, add exactly the URI shown on Bookings → Calendar in your WordPress admin. It looks like:
Copy it from that screen rather than typing it. It must match character for character, includinghttpsand anywww.
https://yoursite.example/wp-admin/admin-post.php?action=varnify_card_google_callback
- Google shows you a Client ID and a Client secret. The secret is shown once, so copy both now.
- Paste them into Bookings → Calendar in WordPress and save, then press Connect.
Card asks Google only for what it needs: permission to read your calendar’s busy times and to create its own events. It cannot read the contents of your appointments.
The one thing that will catch you out
While your consent screen is in Testing mode, Google expires the connection roughly every seven days. The picker keeps working, but it stops seeing your calendar until you press Connect again.
To stop that, set the consent screen to In production (OAuth consent screen → Publish app). For an app that only ever asks for your own account, no review is required.
If the connection drops, bookings still work. You simply lose the “don’t offer times I’m busy” half.