The LatePoint Google Calendar & Meet Addon is a core extension for the LatePoint WordPress booking plugin. It enables real-time synchronization between your website’s booking system and Google’s ecosystem.
This is EXACTLY the same product as distributed by the developer. Sales Page
Current Version: 1.5.7 (as of late 2025/early 2026).
Plugin Weight: Optimized from 17MB down to ~1MB for faster site performance.
PHP Requirement: PHP 7.4 or higher (PHP 8.x recommended).
WordPress Compatibility: Version 6.5 or higher (tested up to 6.9+).
Authentication: Uses OAuth 2.0 (secure token-based access; no Google passwords stored on your server).
| Feature | Detail |
| Sync Type | Two-Way Sync: LatePoint bookings push to Google; Google events pull into LatePoint to block availability. |
| Video Integration | Google Meet: Automatic generation of unique meeting links for specific services. |
| Multi-Calendar | Support for pulling from multiple Google calendars under a single account. |
| Mapping | Assign specific Google Calendars to individual Agents, Services, or Locations. |
| Timezone Logic | Automatic synchronization of timezones to prevent scheduling offsets between client and agent. |
| Templates | Customizable event titles and descriptions using LatePoint variables (e.g., {customer_name}, {service_name}). |
To ensure the addon functions correctly, your server and Google Cloud project must meet the following:
POST Request Access: Your server must allow POST requests to admin-ajax.php. Security plugins or firewalls (like Cloudflare or Wordfence) that block external pings may prevent “Auto-Sync” from working.
Google Cloud Project: Requires a configured project in the Google Cloud Console with the Google Calendar API enabled.
Redirect URI: Your site must be running on HTTPS to satisfy Google’s OAuth requirements.
PHP Limits: max_input_vars should be set to at least 3000 if you have many agents or locations, to avoid data truncation during sync setup.
App Verification: If using a “Personal” Google App, you may see a “Not Verified” warning during setup. This is a Google-side restriction that can be bypassed in the advanced settings during the initial connection.
Caching: You must exclude the customer dashboard and booking pages from server-side or plugin-side caching (like WP Rocket or LiteSpeed) to ensure real-time availability is accurate.
