Overview

We’ve enhanced calendar privacy when accessing accounts via the Login As functionality. Third-party calendar events now consistently respect privacy controls, even when viewed through elevated access.

What’s New

When using Login As functionality:

• The Hide third-party event details setting is not shown in Calendar Settings or My Profile
• Third-party event details are never displayed and will appear as Busy instead
• Event details remain visible only to the event owner

The original behavior remains unchanged:

• If Hide third-party event details toggle is ON → All third-party events show as Busy for others in calendar view
• If Hide third-party event details toggle is OFF → Only private third-party events show as Busy in calendar view

Why It Matters

This enhancement strengthens privacy and security by ensuring third-party calendar details stay protected across all access methods, while preserving existing calendar behavior for end users.

We’re excited to announce that the Service Booking Public API is now live 🎉

This release enables developers and partners to programmatically create, manage, and retrieve service bookings—unlocking deeper integrations and automation around service-based scheduling.

—

📦 What’s Included

The Service Booking Public API supports the complete booking lifecycle:

1. Get All Service Bookings: Retrieve service bookings within a selected date range, with an optional filter of service location.

Docs: <a href="https://marketplace.gohighlevel.com/docs/ghl/calendars/get-service-bookings" rel="ugc nofollow noopener noreferrer" target="blank”>https://marketplace.gohighlevel.com/docs/ghl/calendars/get-service-bookings

Docs: <a href="https://marketplace.gohighlevel.com/docs/ghl/calendars/create-service-booking" rel="ugc nofollow noopener noreferrer" target="blank”>https://marketplace.gohighlevel.com/docs/ghl/calendars/create-service-booking

3. Get Service Booking by ID: Retrieve detailed information about a specific service booking, including services, assigned staff, add-ons (if any), and assigned resources.

Docs: <a href="https://marketplace.gohighlevel.com/docs/ghl/calendars/get-service-booking-by-id" rel="ugc nofollow noopener noreferrer" target="blank”>https://marketplace.gohighlevel.com/docs/ghl/calendars/get-service-booking-by-id

Docs: <a href="https://marketplace.gohighlevel.com/docs/ghl/calendars/update-service-booking" rel="ugc nofollow noopener noreferrer" target="blank”>https://marketplace.gohighlevel.com/docs/ghl/calendars/update-service-booking

5. Delete Service Booking: Delete a service booking. This action will also remove all events associated with the booking.

Docs: https://marketplace.gohighlevel.com/docs/ghl/calendars/delete-service-booking

—

💡 Why This Matters

With the Service Booking Public API, developers can:

• Build custom booking flows for service-based businesses
• Seamlessly sync service bookings with external systems
• Automate booking creation, updates, and cancellations

This release makes service scheduling more flexible, extensible, and scalable for our ecosystem.

—

What's New

The Opportunity Changed trigger now supports event-based operators. Previously, this trigger worked as a filter—firing for any change on opportunities matching specific field values. Now, with Has Changed and Has Changed To operators, you can trigger workflows only when a specific field actually changes.

New Operators for Standard Fields

New Operators for Custom Fields

Why This Matters

Previously, setting a trigger with "Assigned To = John" would fire on every update to John's opportunities—notes, lead value, tags—creating unintended triggers. Now, with "Has Changed To," you can trigger only when the Assigned To field changes to a specific user, ignoring all other updates.

How to Use

Add or edit an Opportunity Changed trigger, select your field (standard or custom), and choose from the new operators. Existing workflows default to "Equals" behavior, nothing breaks.

🧭 Overview

We’re excited to release a comprehensive set of Schedules APIs and documentation, enabling users to create, manage, assign, and query schedules/staff availability across calendars programmatically. These APIs unlock deeper automation, powerful integrations, and precise availability control for teams and users at scale.

🚀 What’s Included

🛠️ Core Schedule Management

• Full CRUD support for creating and managing schedules
• Define rule-based availability (weekday rules and date-specific overrides)
• Support for multiple availability intervals per day

🔍 Discovery & Administration

• Searchable and filterable schedules list
• Pagination and filtering, built for admin dashboards, bulk tools, and analytics

🔄 Schedule–Calendar Associations

• APIs to dynamically assign or un-assign schedules from calendars
• Validations to prevent invalid or cross-location schedule assignments
• Safe handling to avoid orphaned or disconnected calendars

 📅 Event Calendar Support

• Dedicated APIs for managing event calendar-specific availability
• Automatically handles schedule creation and updates for event-based use cases

🎯 Why This Matters

• Provides teams with full programmatic control over schedules and their relationships with calendars
• Helps agencies and locations manage availability across large teams and multiple locations
• Supports dynamic schedule updates based on workflows, staffing changes, or external systems
• Ensures scalable, consistent scheduling logic across the platform

What's New

Autosave now works with AI Builder created workflows. When Autosave is enabled, your AI generated workflows save automatically upon creation and every subsequent AI Builder edit saves in the background.

How It Works

Enable Autosave in global workflow settings, then generate workflows using AI Builder, they'll save automatically. Further edits made through AI Builder continue saving without manual intervention.

Why This Matters

Build confidently with AI without worrying about lost work from forgotten saves, network issues, or browser refreshes.