Tag Archives: Developer

Meet Add-ons SDK available in Developer Preview

What’s changing 

Today, the Google Meet Web Add-ons SDK is available through our Developer Preview Program. Developers can use the SDK to bring their app experience right into Meet. End users can install, open, and collaborate in apps right inside a meeting, either as the meeting focal point, or in the sidebar — all without ever leaving Meet. 


Recently, we announced the availability of the Google Meet API through the Google Workspace Developer Preview Program. The Google Meet Add-ons SDK expands on these platform capabilities and allows developers to integrate apps and workflows directly into the Meet UI. There are two ways in which add-ons show up in Meet: the main stage of a meeting or the meeting side panel. The main stage allows apps to be the focal point of a meeting experience, unlocking the opportunity for add-on users to collaborate while in a meeting. The side panel allows users to to share data, take surveys, or update records while staying focused on the discussion in the meeting.




Partners such as Atlassian, Figma, Lucid, Miro, Read.ai, and Polly.ai have already built and launched Meet Add-ons, and we’re excited to see what other apps and workflows developers will build into Meet’s highly-interactive surfaces.






During Developer Public Preview, add-ons can only be deployed within your domain and are only accessible when using Google Meet on the web. In the coming months, we will also launch Meet Add-ons SDKs for Android and iOS to expand these capabilities to mobile form factors. 


To access the preview SDK, please join the Google Workspace Developer Preview Program.


Who’s impacted

Admins and developers



Why you’d use it 

Using the Google Meet Add-Ons SDK, developers can integrate their apps directly in Google Meet. In turn, meeting participants can leverage these apps to collaborate on a whiteboard, brainstorm with the latest design files, and more all without leaving the Meet user interface.


Getting started

Rollout pace


Availability

  • Available to all Google Workspace customers

Resources


Read and write out of office and focus time events using the Calendar API

What’s changing 

In addition to reading and writing working location data, we’re expanding the Calendar API functionality to encompass out of office and focus time data. Developers can use the API to read and write this information and synchronize users’ availability with external systems. For example, you can use the API in conjunction with HR systems to automatically add OOO entries to a user’s calendar when they submit vacation time. Or the API can be used to automatically block focus time on a user’s calendar to complete training courses. 

  • Reading and writing out of office and focus time is helpful in a variety of situations such as: 
  • Creating and updating OOO and Focus Time events (Events.Insert, Events.Update, Events.Patch). 
  • Specifying OOO and Focus Time specific features, such as auto-declining meetings, and setting do-not-disturb statuses. 
  • Selecting any combination of event types to read from a calendar (Events.List). 

Further, reading and writing this information eliminates the need for users to enter the same information into multiple systems, helping to cut down on manual churn.


Who’s impacted

Developers


Why you’d use it

Out of office and focus time event support joins support for working location, which was announced earlier this year, to round out API functionality for calendar events. Each specific event type can be synced throughout your organization's IT ecosystem, creating seamless user journeys and helping to connect users with resources and each other. This includes things such as:


  • Mapping working location data to better adapt on-site resources and update other third-party surfaces, such as hot desk booking tools. 
  • Automatically blocking OOO based on vacation or PTO requests.
  • Blocking off focus time events to give users time to go through onboarding or other company training programs.


Additional details

Prior to this update, if you requested to read a user’s calendar via API v3, out of office and focus time events were returned with [email protected] in the organizer field, and without their specific features. With this update, these events will return with all their properties and the specific user as organizer. Please check your code to ensure it does not make implicit assumptions about the previous API return values, and use the eventType parameter to perform different operations with regular, OOO, Focus Time, or Working Location events 


Getting started


Rollout pace

Availability

  • The Calendar API is available to all. 

  • Out of Office events are available to Google Workspace Essentials, Enterprise Essentials, Frontline, Enterprise Starter, Enterprise Standard, Enterprise Plus, Nonprofits, Business Starter, Business Standard, Business Plus, Education Fundamentals, Education Standard, and Education Plus customers.

  • Focus Time events are available to Google Workspace Enterprise Starter, Enterprise Standard, Enterprise Plus, Nonprofits, Business Standard, Business Plus, Education Fundamentals, Education Standard, and Education Plus customers.

Resources


Google Meet API now available in Developer Preview

What’s changing 

Launching through our Google Workspace Developer Preview Program, developers can now use the Google Meet API. Using this API, developers can:

  • Programmatically create and configure Meet calls. 
  • Retrieve information about past meetings, such as the meeting times and attendees. 
  • Access meeting artifacts, such as transcripts and video recordings. 
  • Subscribe to real time updates on meetings, such as when a participant joins or leaves. 

The API will give partners and customers the ability to create and configure Meet video conferences, allow their end users to join a conference, and post real-time updates from within their own applications.


Using the Meet API, Outreach is ingesting meeting recordings and transcripts into their AI-powered conversation intelligence tool, Kaia, to deliver rich insights to their teams.


Who’s impacted

Developers


Why you’d use it

Incorporating your product with the Google Meet API streamlines workflows and provides your product with Meet information that easily enhances your product offering. For example, partners such as Hubspot, Outreach, Salesloft and Salesforce currently integrate the Meet API to pull meeting recordings and artifacts into their conversational intelligence tools for analysis and sales coaching.


Additionally, integrating with the Google Meet API enables you to link your app with Meet’s video conferencing capabilities, allowing users to access a secure video conferencing product from their own UI by the click of a button. Brandlive, a leading webinar and event platform, uses the Google Meet API as a way to create and configure video sessions for larger sessions and smaller breakout conversations.


Additional details

View the Google Meet API documentation for additional details.


Getting started



Rollout pace


Availability

  • Available to all Google Workspace customers

View & compare script versions with Apps Script project history

What’s changing 

As we continue to improve the experience for Apps Script developers, today we're announcing project history, a new interface for developers to view previously deployed script versions and compare versions to the current script version. 


Developers can use project history to view the code of previously deployed script versions. The highlight changes can be used to quickly compare differences between their selected version and the current, or head, version, taking the guesswork out of determining what's changed. Anyone who has edit permission on an Apps Script project can access project history. To navigate to the project history page, open an Apps Script project and click Project History.

The project history page displays up to 200 previously deployed versions and the head version of the script.


To compare a version to the head version, turn on Highlight changes.



Additional improvements for script versions will be made in the coming weeks.





Who’s impacted

Developers

Why it’s important

Apps Script is a low-code development platform that makes it quick and easy to build business solutions that integrate, automate, and extend Google Workspace. With Apps Script, Google Workspace users can customize workflows, create automations, and build integrations that connect the applications they use every day.

Getting Started

  • Developers: Use our developer documentation to learn more about working with Apps Script and watch the video below to see project history in action:

  • Anyone who has edit permission on an Apps Script project can access project history. To navigate to the project history page, open an Apps Script project and click Project History.


Rollout


Availability

  • Available to Google Workspace customers
  • Available to users with a personal Google account

Resources


Programmatically read and write working locations with the Calendar API, now generally available

What’s changing 

Previously available in beta through our Developer Preview Program, the ability to read and write a user’s working location using the Calendar API is now generally available. 


Reading a user’s working location helps better understand the flow and volume of people through physical campuses. Using this information, you can better adapt on-site resources and update other third-party surfaces, such as hot desk booking tools. 


Writing a user’s working location makes it easier to update a user's working location in their calendar based on when and where they’ve booked a hot desk, or if they’ve scheduled a trip via a travel booking tool, and more. 


Getting started 



Rollout pace


Availability 

All developers can use the API, however the working location feature is only available for eligible Workspace editions: 
  • Available to Google Workspace Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Fundamentals, Education Plus, Education Standard, the Teaching and Learning Upgrade and Nonprofits customers, as well as legacy G Suite Business customers 
  • Not available to Google Workspace Essentials, Business Starter, Enterprise Essentials, Frontline, G Suite Basic customers 

Resources 

Programmatically read and write working locations for a portion of the day with the Calendar API

What’s changing 

Recently, we introduced the ability for users to set working locations in Calendar that indicate where they’re working for specific portions of the day. Now, we’re adding the ability to programmatically read and write working locations for specific portions of the day. This update expands on the existing reading and writing functionality announced earlier this year. 


Getting started 


Rollout pace 

  • This feature is available now for all eligible Google Workspace editions. 

Availability 

All developers can use the API, however the working location feature is only available for eligible Workspace editions: 
  • Available to Google Workspace Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Fundamentals, Education Plus, Education Standard, the Teaching and Learning Upgrade and Nonprofits customers 

Resources 

Ability to create spaces, memberships, group chats, and more using the Google Chat API is now generally available

What’s changing 

Last year, we announced that developers could use the Google Chat API to programmatically create new spaces and add members to those spaces through the Google Workspace Developer Preview Program. 

Today, those features are generally available for all Google Workspace developers, along with the ability to use Chat API to: 


Who’s impacted


Admins and developers


Why you’d use it 

These features enable developers to build solutions that integrate into workflows and pull contextual data right into the conversation. Using the new API functionalities, you can set up new spaces that focus on a specific topic, team, or project. You can also use the new APIs to encourage collaboration and outreach with users in your organization. For example, LumApps, a leading intranet platform, enables you to start a direct message in Google Chat from its user directory. Those who are trying to find others based on job titles, roles, departments, and other attributes, can quickly start messaging each other.




Additional details

To ensure you are aware that a Chat application has performed an action on behalf of a user, Chat web and mobile apps will display the app name for system messages and Chat messages. 




Getting started

  • Admins: Admins can use the API controls in Admin Console if they want to restrict access to Google Chat data.
  • Developers: Access the new Chat APIs through the Google Chat API


Rollout pace


  • This feature is now available.

Availability

  • Available to all Google Workspace customers.

Launching in beta: programmatically write working locations with the Calendar API

What’s changing 

Available now in beta through our Developer Preview Program, you can write a user’s working location using the Calendar API. 


Using the API to write a Calendar user’s working location values can help you synchronize users' working location with third-party tools. You can easily update users’ working location based on: 
  • When they book a hot desk via a hot desk booking tool 
  • Schedule a trip via a travel booking tool 


Reading of working locations is already available through the Developer Preview Program. 

Getting started 


Rollout pace 

  • This feature is available now for all eligible Google Workspace editions. 

Availability 

All developers can use the API, however the working location feature is only available for eligible Workspace editions: 
  • Available to Google Workspace Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Fundamentals, Education Plus, Education Standard, the Teaching and Learning Upgrade and Nonprofits customers

Resources 

Launching in beta: manage working locations with the Calendar API

What’s changing

Available now in beta through our Developer Preview Program, you can read working location data using the Calendar API and get notified when those working locations change. Previously, we said this functionality would be available through a separate API. However, in order to provide a more streamlined experience, this functionality will be instead available in the Calendar API. 

Using the API to read a Calendar user’s working location values can help you:

  • Analyze the flow and volume of people through physical campuses, helping you adapt on-site resources to the needs of your employees.
  • Share whereabouts across other internal or third-party surfaces, making it easier to enable tasks such as hot desk booking or schedule in-office or remote working days.

We anticipate write support for the API to become available in Q3 2023 — we’ll share an update here on the Workspace Updates Blog at that time.

Getting started


Admins and Developers: 

Admins: 

Availability

While all developers will be able to use the API, the working location feature is only available for eligible Workspace editions:

  • Available to Google Workspace Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Fundamentals, Education Plus, Education Standard, the Teaching and Learning Upgrade and Nonprofits customers, as well as legacy G Suite Business customers 
  • Not available to Google Workspace Essentials, Business Starter, Enterprise Essentials, Frontline, G Suite Basic customers 

Resources


Introducing Trusted Types in Google Workspace

What’s changing

We’re improving the client-side security of Google Docs, Sheets, Slides, Forms, Sites, Jamboard, Drawings, and Drive with Trusted Types. This will provide an extra layer of protection around Document Object Model (DOM) APIs that are used by the apps listed above or third-party extensions. 

This new enforcement mode will require third-party extensions to use typed objects instead of strings when assigning values to DOM APIs, and will begin rolling out on March 23, 2023. Once Trusted Types are fully enforced, the Trusted Types directive will be present in the Content Security Policy (CSP) header: 

Who’s impacted

Developers (relying on any Chrome extensions that modify DOM APIs.) 


Why it’s important

Trusted Types is a feature that further enhances our advanced data protection controls to keep users and data safe across more of the apps they use everyday. 


Additional details 

Screen readers, braille devices, and screen magnification will not change with Trusted Types. However, we recommend admins and developers check third party extensions for Trusted Types violations. Visit the Help Center to learn more about Accessibility for Google Docs, Sheets, Slides, & Drawings


Getting started 

  • Admins: There is no admin control for this feature. 
  • Developers: 
    • To make code Trusted Types compliant, signal to the browser that data being used within the context of these DOM APIs is trustworthy by creating a Trusted Type special object. 
    • There are several ways to be Trusted Types compliant, such as removing the offending code, using a library, or creating a Trusted Types policy. To ensure a seamless experience for users, these techniques can be employed before Trusted Types enforcement is rolled out. 
    • Visit the Chrome DevTools engineering blog to learn more about implementing CSP and Trusted Types debugging in Chrome DevTools
  • End users: There is no end user setting for this feature. 

Rollout pace 

Availability 

  • Available to all Google Workspace customers, as well as legacy G Suite Basic and Business customers 
  • Available to users with personal Google Accounts 

Resources