AppsScriptPulse

Official News

Q1 2026 Developer Roundup: Vertex AI, Agentic Add-ons, and the Growth of Workspace Studio

Tags:
| | 0 Comments |

Q1 2026 Developer Roundup: Vertex AI, Agentic Add-ons, and the Growth of Workspace Studio

The first quarter of 2026 has been a significant period for the Google Workspace ecosystem, primarily focused on providing the tools needed to scale the “agentic” workflows we saw emerging late last year. From the arrival of the Vertex AI Advanced Service in Apps Script to the full rollout of Google Workspace Studio, the platform is becoming increasingly integrated and capable of supporting sophisticated, AI-driven automations.

Apps Script: AI is Now an Advanced Service

For many Apps Script developers, the standout update this quarter is the arrival of the Vertex AI Advanced Service. Launched in January, this service allows you to call the Vertex AI API and prompt Gemini models directly within your projects, removing the previous reliance on UrlFetchApp.

While the service represents a step forward by handling authentication natively, it currently has some limitations. As noted in our January deep dive, while the connection is simplified, it lacks support for key features like Grounding with Google Search or the specialised Image Generation and Editing models available in the broader Vertex AI API. For developers requiring these advanced capabilities or alternative authentication methods, such as service accounts, the manual UrlFetchApp approach remains a necessity for now, though we hope to see these gaps closed in future iterations.

Google Workspace Studio

As of March 19, 2026, Google Workspace Studio (formerly Workspace Flows) has launched to all Rapid and Scheduled Release domains. It provides a centralised hub for creating and managing AI agents without needing extensive code.

Looking ahead, we’re expecting even more extensibility. It hopefully won’t be long until the initially announced features, including the ability for agents to call external APIs via webhooks and the integration of custom Apps Script steps, are released. These additions will allow developers to bridge the gap between low-code convenience and the complex logic required for internal proprietary tools.

Google Chat: The Add-on Evolution & Interactive Cards

We’ve seen a continued effort from Google to unify the developer experience in Google Chat. A major milestone is the ability to convert interactive Chat apps into Google Workspace Add-ons. This allows for a single distribution through the Marketplace that can extend Chat alongside Gmail, Calendar, and Docs.

This shift is supported by the general availability of the AddOnsResponseService, along with Cloud Pub/Sub and Dialogflow integrations for Chat-based add-ons. Additionally, a new Developer Preview launched in March allows Chat apps to create and asynchronously update card-based messages on behalf of users.

Gmail & Postmaster Tools v2

For those managing high-volume email workflows, the Gmail Postmaster Tools API v2 reached general availability in February. This version provides deeper access to the full Postmaster Tools dataset, including compliance status and the queryDomainStats method for more flexible reporting on sender reputation.

Security, Permissions, and API Graduations

Governance and security remain a priority, with several key updates affecting how we manage data and access:

  • Drive API Access: The enforceExpansiveAccess parameter is now deprecated. To restrict access, developers are encouraged to use the “folders with limited access” configuration.
  • Secondary Calendar Management: Following community feedback, Google has postponed the deletion of orphan secondary calendars for paid accounts until October 5, 2026. To assist with this transition, a new Calendar API endpoint will launch by June 2026, allowing administrators to programmatically transfer ownership of individual secondary calendars.
  • Google Meet Security: Updated guidance advises against reusing Meet codes across different Calendar events to prevent unintended access. Developers should generate a unique conference using the createRequest field for every new event.
  • Granular OAuth: A gradual rollout of the granular OAuth consent screen has begun for Chat apps built with Apps Script, offering users more control over specific scope grants.
  • Classroom API: Student Groups endpoints have graduated to General Availability, enabling programmatic management of group memberships.
  • Marketplace API Deprecation: The licenseNotification resource has been deprecated. While there is no direct replacement, developers can monitor install events via Google Analytics.

Relational Power: JDBC Supports PostgreSQL

While not in the official release notes, a significant update for the community is the addition of PostgreSQL support to the Apps Script JDBC service. By supporting the jdbc:postgresql:// protocol, developers can now connect their automations directly to relational databases, moving beyond the traditional limits of Google Sheets for data storage.

The Road Ahead

The pace at which features are moving from Developer Preview to General Availability indicates a platform that is maturing rapidly. The roadmap for Google Workspace Studio also hints at extensibility including the anticipated release of custom triggers and actions built with Apps Script, a dedicated connectors platform for third-party tools like Jira and Salesforce, and the ability to integrate custom Vertex AI models directly into workflows will represent a fundamental change in how we handle complex data processing within Workspace automations.

Official News

Q4 2025 Developer Roundup: AI Agents, Custom Chat Workflows, and the Future of Apps Script

Tags:
| | 2 Comments |

The final quarter of 2025 has been a transformative period for the Google Workspace ecosystem, centred on the evolution of “Agentic” workflows. With the transition of Google Workspace Flows into the newly branded Google Workspace Studio, developers now have a centralised platform for building AI-powered automations. From deep Chat customisation to enhanced Meet artifacts, here’s a roundup of the key updates from October, November, and December that you need to know about.

Google Workspace Studio & Add-ons

The most significant shift this quarter is the general availability of Google Workspace Studio (formerly Workspace Flows). This platform allows developers to build AI agents that automate everyday work across the ecosystem.

  • Studio Extensions: Developers can now build Google Workspace Add-ons that extend Studio, allowing for custom logic and integrations within AI-driven processes (this feature is in “Limited Preview” likely due to the extended rollout period for Workspace Studio).
  • Dialogflow Integration: In a new developer preview, Chat apps built as Google Workspace add-ons can now use Dialogflow CX and Dialogflow ES, enabling more sophisticated natural language conversations within the Workspace interface.

Google Chat API: Deep Personalization

The Chat API received continued substantial updates focused on helping users organise information and enhancing app interactivity.

  • Custom Sections: A major developer preview now allows the Chat API to programmatically create and manage custom sections. Developers can now create, delete, and position these sections to organise conversations in a personalised view.
  • Membership Roles: Membership management has been refined with the introduction of new role types. In the Chat UI, existing space managers are now Owners, and a new Manager role (Role Assistant Manager) has been added to help administer spaces.
  • Rich Links and Accessories: Generally available updates include support for reading rich links to Gmail threads and the ability for Chat apps to include interactive accessory widgets in private messages.

Google Meet: Working with Artifacts

Real-time data accessibility was a core focus for Meet this quarter, particularly around the Developer Preview Program.

  • Smart Notes Retrieval: You can now retrieve smart notes files in a conference record using the get and list methods on the smartNotes resource.
  • Event Subscriptions: Calendar invitees can now receive started and transcript generated events through the Google Workspace Events API.
  • Meeting Identification: New fields for phoneAccess and gatewaySipAccess have been added to the spaces resource to help identify and join meeting spaces.

Google Drive API

  • Comment and Reply Events: In a new developer preview, developers can now subscribe to comment and reply events in Google Docs, Sheets, and Slides. This is a powerful feature for building reactive applications that monitor file collaboration in real-time.

Gmail & Calendar: Ownership and Insights

  • Postmaster Tools v2: The Gmail API v1 now offers a developer preview for Postmaster Tools v2. This includes compliance status data and the queryDomainStats method for flexible querying.
  • Secondary Calendar Ownership: As of November, secondary calendars have moved to a single data-owner model. This change restricts the ability to delete or manage secondary calendars to the designated data owner, preventing unintended actions across organisations.

The Road Ahead

This quarter has shown a clear trajectory toward more intelligent, “agentic” integrations within Google Workspace. From the rollout of Google Workspace Studio to the granular control provided by new Chat and Drive events, the platform is becoming increasingly responsive to automated workflows.

It will be exciting to see how the community uses these new capabilities in the coming months. As for the future of Apps Script, Q1 2026 I think will be very exciting, stay tuned!!!

Official News

Q3 2025 Developer Roundup: Chat App Authentication, Granular Control and More

Tags:
| | 0 Comments |

The third quarter of 2025 has been a busy one, with a host of updates across various APIs. This quarter, there has been a strong focus on enhancing app authentication, improving API capabilities, and providing more granular control for Google Drive. Here’s a roundup of the key updates from July, August, and September that you need to know about.

Chat API

The Chat API has received a number of significant updates, with a strong emphasis on expanding the capabilities of Chat apps through app authentication. In a new developer preview, several methods, including those for getting and listing space events, now support app authentication with administrator approval. This allows apps to act on behalf of a user who has granted consent, opening up new possibilities for automation and integration.

In addition to the new authentication features, the Chat API now allows for the creation of carousels in card messages, providing a richer and more interactive user experience. We’ve also seen an increase in per-space quota limits for writing messages and reactions, which will be a welcome change for high-traffic apps.

Other notable updates for the Chat API include the ability to quote messages, read metadata for various chip types, and the general availability of building Chat apps as Google Workspace Add-ons.

Google Workspace Admin SDK

The Admin SDK has seen several important updates in Q3, particularly within the Reports API. Developers can now get activity events forGmail andGemini in Workspace Apps, providing greater insight into how these tools are being used within an organisation.

A key feature for Drive management is the introduction of activity events for pre-fetched content, allowing administrators to better monitor and understand data access patterns.

Gmail API

The Gmail API has introduced Deal Cards in the Promotions tab, allowing developers to create more engaging and actionable promotional content. For organisations using client-side encryption, the API now supports smart cards, enhancing security for sensitive communications.

Google Drive API

A significant change has been made to how download, print, and copy restrictions are applied, giving owners and organisers more granular control over content. Previously, these restrictions could only be applied to users with reader roles, but now, owner and organizer roles can extend these restrictions to users with writer permissions as well.

For individual files, developers should now use the itemDownloadRestriction field, with the corresponding capabilities.canChangeItemDownloadRestriction field available to check modification permissions. Similar controls have been introduced for shared drives, using the downloadRestriction field within the Restrictions object. While the previous copyRequiresWriterPermission field remains, its functionality has changed, and Google recommends using the new system to manage content restrictions.

For developers working with events, the Drive API, in conjunction with the Google Workspace Events API, now supports subscriptions to a variety of Drive events, including file additions, moves, edits, and access proposals. This is a powerful feature for building reactive and real-time applications.

Google Workspace Events API

The Events API has been a major focus this quarter, with new features for both Chat and Drive. As mentioned the ability to subscribe to Drive events is a significant step forward, enabling developers to build applications that respond in real-time to changes in a user’s Drive.

For Chat, the Events API now allows apps to subscribe to space events using app authentication with administrator approval, further expanding the capabilities of Chat apps.

Google Workspace Add-ons

The big news for add-on developers is the ability to build Google Chat apps as Google Workspace Add-ons, which is now generally available. This provides a unified framework for extending the functionality of Google Workspace applications.

Key Deprecations and Breaking Changes

As with any quarter, there have been some deprecations and breaking changes to be aware of:

It will be exciting to see what the community builds with these new tools!

Add-on, Official News

Granular Consent for Published Google Workspace Editor Add-ons: What Developers Need to Know

Tags:
| | 0 Comments |

This screenshot shows the new OAuth consent screen, which lets the user provide consent for a subset of the requested OAuth scopes. (Image credit: Google)

Earlier this year, we launched an improved version of the OAuth consent screen to the Apps Script IDE and unpublished Editor Add-ons that allows users to specify which individual scopes they would like to authorize for that script. For example, if a script requests access to a user’s Sheets and Forms files, and the users only intends to use the script with Sheets files, they can decide to only allow access to their spreadsheets and not their forms.

Google is continuing to enhance user privacy and control by extending the granular OAuth consent screen to published Editor Add-ons. This latest move builds upon the changes first introduced to the Apps Script IDE back in January, which we covered in detail at the time.

For those who missed it, this feature allows users to choose exactly which permissions (scopes) an application can access, rather than being forced into an “all-or-nothing” decision.

What’s Changing Now?

This more granular consent experience will now be presented to users when they install or re-authorize published Editor Add-ons from the Google Workspace Marketplace. When an add-on requests access, for instance to both a user’s Docs and Sheets, the user can now choose to approve one, both, or neither of those permissions.

While Google notes that “Pre-existing scope grants will not be affected”, it’s crucial for publishers of existing add-ons to understand that this new consent screen will appear if a user needs to re-consent. This can happen for several reasons, such as a user manually revoking the add-on’s access from their Google Account, or if a refresh token expires (e.g., after six months of inactivity). In these cases, existing users will be presented with the new granular options, and developers must be prepared for the possibility of partial authorisation.

A Reminder for Developers

As this functionality rolls out, starting on August 19 2025, it’s crucial for developers to ensure their add-ons can handle partial consent. If a user denies a specific scope that is essential for a feature, the add-on should fail gracefully without breaking.

As we detailed in our January post, the ScriptApp and AuthorizationInfo classes are your key tools for managing this. These allow you to programmatically check the granted scopes and build safeguards into your code. For a deeper dive into the methods and a guide on handling these scenarios, we recommend reviewing our original article.

Source: Granular OAuth consent in Google Apps Editor Add-ons

Official News, Solutions, Drive, Workspace Events API

Modernising Drive Monitoring: The Google Drive Events API is Now in Public Preview

Tags:
| | 0 Comments |

Google Drive is now integrated with the Workspace Events API, which allows third-party developers to create subscriptions on Drive items and receive notifications via Cloud Pub/Sub when those resources change. This offers developers a more reliable, featureful way of receiving events over the current files.watch and changes.watch methods that exist today.

Good news for developers working with Google Drive! Google has just announced that the Google Drive Events API is now available in a Developer Public Preview. This is a significant update for anyone who needs to track changes to files in Google Drive, offering a more robust and feature-rich way to receive notifications.

For a long time, developers have relied on the files.watch and changes.watch methods to monitor file changes. Whilst these methods have been useful, the new Drive Events API, integrated with the Google Workspace Events API, promises a more reliable and scalable solution.

What can you do with the new API?

The new API allows you to subscribe to events on Drive items and receive notifications through Cloud Pub/Sub. In this initial public preview, the following events are supported:

  • A file has been added to a folder or shared drive.
  • A file has been moved to a folder or shared drive.
  • A file has been edited, or a new revision is uploaded.
  • A file has been trashed or restored from the trash.
  • An access proposal has been created or resolved for a file.

This opens up a whole range of possibilities for building powerful applications that react in real-time to changes in Google Drive. Imagine creating automated workflows that trigger when a new file is added to a specific folder, or a security tool that alerts you when a sensitive document is moved or trashed.

How to get started

To start using the new Google Drive Events API, you’ll need to be enrolled in the Workspace Developer Public Preview program. Once you’re in, you can find the relevant documentation and getting started guides on the Google Developers site.

A Note for Google Apps Script Developers

You can absolutely use Google Apps Script to make the API calls to create and manage your event subscriptions. However, it is important to be aware that receiving the actual notifications requires a different approach to traditional Apps Script triggers.

The Drive Events API delivers all notifications to a Cloud Pub/Sub topic. This means you will need a Google Cloud Platform (GCP) project to handle these incoming messages. It’s also important to note that, according to the documentation, the Pub/Sub topic you use for notifications must be in the same Google Cloud project that you use to create the event subscription itself.

These new capabilities hopefully unlock some more efficient ways for developers and third parties to monitor Google Drive content.

Source: Google Drive Events API now available in Developer Public Preview

Official News, AI, AppSheet, No Code

It’s Official: Gemini in AppSheet is Now Generally Available for Enterprise Users

Tags:
| | 0 Comments |


We’re very excited to announce that Gemini in AppSheet Solutions is now Generally Available (GA)! This powerful capability allows AppSheet Enterprise Plus users to integrate Google’s Gemini directly into their automation workflows.

Following our previous post announcing the public preview, we are excited to share that Gemini in AppSheet Solutions is now generally available (GA) for all AppSheet Enterprise Plus users. This update allows creators to directly integrate Google’s Gemini models into their automation workflows, making AI-powered automation more accessible than ever.

What This Means for Creators

This move to general availability solidifies the simplified AI integration within AppSheet. Instead of complex setups involving API keys and external scripts, creators can now use a native “AI Task” step within their AppSheet automations. This new task can handle jobs like extracting specific data from uploaded photos or PDFs, and categorising text directly within AppSheet.

The GA release also brings enhanced confidence in building AI-powered solutions. The in-editor task testing feature allows creators to test and refine AI prompts and configurations with sample data before deployment. This is a crucial step for ensuring reliable AI, and it allows for much quicker iteration.

For administrators, the AppSheet admin dashboard now provides visibility into Gemini usage within the organisation, and allows for control over which creators can use these new features.

Key updates since Public Preview

For creators, the GA release includes a number of improvements:

  • AI tasks now support more column types, including REF types, allowing you to use information in linked tables.
  • The quality of AI responses has been improved for certain data types.

For admins, the AppSheet admin console now shows your organisation’s credit entitlement and consumption, providing insights into how your users and applications are using Gemini.

The Power of the Underlying Model

It’s also worth noting that the underlying Gemini models are market leaders and are continuously improving. New tools on the horizon, such as ‘URL context’ and the ability to also ground results with Google Search, will hopefully filter through to AI Tasks in AppSheet enabling creators to build even more powerful solutions. These advancements will allow for the creation of sophisticated AI assistants that can use real-time information, all without the need for fine-tuned models or complex custom integrations.

Getting Started: Example Template

The announcement post includes links to the relevant documentation for creators and admins. For those looking for a practical example, the AppSheet team has provided a “Book tracking with Gemini” template. This app showcases how you can upload a picture of a book cover, and then use two different AI tasks to automatically extract book-related information and categorise it by genre. I found this to be an excellent starting point for understanding how to implement these new features in your own projects.

Source: Gemini in AppSheet now Generally Available for Enterprise users!

Official News, Solutions, Sheets, Intermediate

Bring Your Data to Life: Smart Chip Read/Write Support Comes to the Sheets API

Tags:
| | 0 Comments |

Last month, we introduced the ability to take basic actions to create and modify tables via the Google Sheets API. This week, we’re expanding the API functionality to include the ability to write and read file and people smart chips.

Following last month’s update for tables, it was recently announced that the Google Sheets API now allows developers interact with the file and people smart chips. This update provides developers with direct access to manage these types of smart chips, which were previously only available through the user interface. For detailed documentation and code snippets on implementation, refer to the official Google Developers support page.

Here is a quick overview of what you can do:

  • Reading Smart Chips: You can retrieve data for all smart chips within a cell. The API response will detail the properties for chipped sections of text and will also identify the plain text sections of the cell. As noted in the documentation to get the chip’s display text, you must request the formattedValue.
  • Adding Smart Chips: You can now insert smart chips for people and files into cells.
    • People Chips: These can be created to link to an individual using their email address. You can also specify the display format for the person’s name.
    • Rich Link Chips: These can be used to create a chip that links to a Google Drive file. Note that writing these chips requires your application to have at least one Drive OAuth scope.

In the feature image above you can hopefully see how a recruitment tracker could be created and read. In the example people chips are used for the ‘Applicant’ and ‘Interviewer’ columns, providing immediate access to contact information. A file chip is used in the ‘Resume’ column to link directly to the candidate’s document in Google Drive. A developer could automate this entire process. For instance, a script could be triggered when a new application is submitted, automatically adding a new row to the tracker complete with the relevant person and file chips, streamlining the entire recruitment workflow.

For those using Google Apps Script, these new functionalities are accessible via the Google Sheets Advanced Service. This update provides better methods for managing smart chips in Google Sheets.

Source: Support for file and people smart chips now available with Google Sheets API

Official News, Intermediate, Sheets

Simplify Google Sheets Table Management with New API Support

Tags:
| | 3 Comments |

Following the improvements made to tables in Google Sheets in March and April, we’re excited to introduce API support for tables. Now, users will be able to take basic actions to create and modify tables via the Sheets API.

Following enhancements to Google Sheets tables last year, Google recently highlighted an update for developers: the Sheets API now supports tables. This is great news for the Google Workspace developer community, as it allows for direct programmatic creation and modification of tables, moving beyond previous reliance on workarounds.

For a while, developers have found clever ways to interact with table-like structures, such as Kanshi Tanaike’s notable 2024 solution using a mix of Apps Script and Sheet formulas. While these methods were very clever, the new, direct API support offers a more robust and straightforward way for interacting with tables in Google Sheets. For Google Apps Script users, for now this will require using the Google Sheets Advanced Service to call these new table methods, as direct integration into the SpreadsheetApp service hasn’t been announced at this time.

Key API Capabilities for Tables:

The Sheets API now lets developers:

  • Add Tables: Create tables with defined names, ranges, and specific column properties (like ‘PERCENT‘ or ‘DROPDOWN‘ with validation).
  • Update Tables: Modify table size (add/remove rows/columns), and toggle table footers. The API also provides methods like InsertRangeRequest and DeleteRangeRequest for more granular control.
  • Append Values: Easily add new rows to the end of a table using AppendCellsRequest, which intelligently handles existing data and footers.
  • Delete Tables: Remove entire tables and their content (DeleteTableRequest) or just the formatting while retaining data (DeleteBandingRequest).
  • Utilise Column Types: Work with various column types including numeric, date, dropdown, smart chip, and checkbox.

For further details, the official Google Workspace Updates blog and the Sheets API developer documentation on tables are your best resources.

Community News, Official News

Google Cloud Next ’25 Developer Spotlight: Diving Deep into Flow, AI & the Future of Workspace Automation

Tags:
| | 0 Comments |

I was thrilled to be invited by Chanel Greco (Google Workspace Developer Advocate) to join Vinay Vyas (Software Engineer, Google) and Steve Bazyl (Developer Program Engineer, Google) for a Developer Spotlight session recorded at Google Cloud Next ‘25.

We explored the exciting evolution of Google Workspace development, focusing on the tools and technologies shaping the future of automation and AI integration.

What We Covered:

  • The Rise of Flows for Workspace Automation: We kicked things off discussing the potential of Flows, a powerful new tool Google had just announced which is designed to simplify task automation in Google Workspace. We explored how developers can tap into its potential by building custom actions, including integrating with Vertex AI [01:17].
  • Extending Capabilities with Apps Script: Your existing Apps Script skills remain crucial! We discussed how they empower developers to extend Flows capabilities as the product evolves [02:08], offering significant opportunities within this user-centric automation tool [01:52].
  • Workspace as an Integrated Platform: Learn about the ongoing efforts to enhance connectivity with third-party services [02:35] and how add-ons (including Chat apps deployed as add-ons [03:32]) are key to keeping users productive within the Workspace context [02:52].
  • The Gemini Effect on Development: Hear our experiences with Gemini 2.5 and its significant impact on code development, particularly for Apps Script [05:29]. We discuss its impressive ability to generate substantial, high-quality code for complex tasks [06:35].
  • AI Agents & The Future: We explored the concept of AI Agents powered by Gemini within Google Apps Script for automating tasks using natural language and discussed the exciting prospects for deeper Gemini integration directly within Apps Script [14:41]. I checky asked Steve if there was going to be a Gemini Advanced Service for Apps Script (you’ll have to watch the video to find out the answer :).

Why Watch?

If you are interested in understanding the future direction of Google Workspace development, this discussion hopefully provides some practical perspectives and explores exciting possibilities.

Source: Developer Spotlight – Google Cloud Next 2025 Special Edition

Official News, Solutions, AppSheet, No Code

AppSheet Gains Gemini Smarts: Native AI Tasks Simplify Automation (No Apps Script Needed!)

Tags:
| | 0 Comments |

Image credit: Google

We’re thrilled to announce that Gemini in AppSheet Solutions is now available in Public Preview for Enterprise users! As announced during the AppSheet breakout session at Google Cloud Next 2025 just a few weeks ago, this powerful new capability allows AppSheet Enterprise Plus users to integrate Google’s Gemini models directly into their automation workflows.

Google recently announced some exciting developments for AppSheet, with the news that creators can now directly integrate Gemini AI capabilities into your AppSheet apps. While developers have previously found ways to connect AppSheet to Gemini including using Google Apps Script (like the invoice processing example using the GeminiApp library previously discussed on Pulse), this new update promises to make AI-powered automation accessible to everyone, no coding required.

What This Means for AppSheet Creators

This move significantly lowers the barrier for integrating AI into AppSheet workflows. Instead of setting up API keys, writing Apps Script functions, and managing libraries like GeminiApp to call the Gemini API for tasks like data extraction, creators can now use a native AI Task step within AppSheet automations.

As highlighted in Google’s announcement, this new approach offers several advantages:

  • Simplified AI Integration: The native AI Task aims to handle jobs like extracting specific data from uploaded photos or PDFs and categorising text – directly within AppSheet. This replaces the need for external scripts for many common AI tasks.
  • Build with Confidence: The GA AI Task Step Testing feature allows creators to test and refine AI prompts and configurations directly in the editor using sample data before deployment, a crucial step for reliable AI.
  • No-Code Accessibility: By embedding Gemini capabilities directly, AppSheet makes powerful AI accessible to creators who may not have coding expertise.
  • Controlled Deployment & Oversight: Admins still control feature access, and workflows can still incorporate human review steps alongside the AI Task.

Potential Use Cases

Google suggests the AI task can be used for:

  • Information Extraction: Getting details from images (serial numbers, meter readings) or documents (PO numbers, tracking info, report details).
  • Record Categorisation: Classifying expenses, maintenance requests, or customer feedback automatically.

These are similar goals to what was achievable via Apps Script previously, but now potentially much simpler to implement directly in AppSheet.

A Big Step for No-Code AI

This native integration represents a significant simplification compared to earlier methods requiring Apps Script. By embedding Gemini directly into AppSheet automations, Google is making advanced AI capabilities much more accessible for business users of all levels.

For full details and setup instructions, refer to the official Google announcement and linked resources.

Source: Gemini in AppSheet now in Public Preview for Enterprise users! (And AI task testing is GA!)