Google Workspace Studio flows get custom triggers, Apps Script steps, third-party integrations, and webhooks
Google adds four new automation capabilities to Workspace Studio Flows, with admin controls from 17 September and end-user features from 21 September 2026.
Google Workspace Studio has been quietly growing into a serious automation platform since its launch in late 2025. The latest update adds four distinct capabilities to flows: custom starters, custom steps, third-party integrations (in beta), and outbound webhooks. Together, they push Studio considerably closer to the kind of cross-platform automation that previously required dedicated tools like Zapier or Make.
Admin console controls started rolling out on 17 September 2026, with end-user features following on 21 September 2026 for Rapid Release domains and from 30 September 2026 for Scheduled Release domains. All four features are off by default, so nothing changes for your users until an admin switches them on.
What’s actually being added
Custom starters
A starter sits at the very beginning of a flow and listens for an event. Previously, flows could only be triggered by events within Google Workspace apps. Custom starters extend that to external applications, including third-party webhooks. When the event fires, the starter captures the relevant details, packages them as data variables, and kicks off the rest of the flow.
In practice, this means a flow can now start because something happened in another tool entirely, not just because someone created a file in Drive or sent a message in Chat.
Custom steps (Apps Script)
Custom steps let you drop Google Apps Script logic directly into the middle of a flow. If your organisation already uses Apps Script for any automation, this is a significant addition. You can wire your existing scripts into a flow as a discrete step, rather than maintaining separate, disconnected automations.
The platform is designed to be accessible to people with basic scripting knowledge. You do not need to be a developer, but you do need to be comfortable reading and writing simple functions.
Third-party integrations (beta)
This is the headline addition for most teams. Studio can now connect directly to Asana, Confluence, HubSpot, Jira, Mailchimp, QuickBooks, Salesforce, and Slack as flow steps, passing data between Workspace and those services without manual copying or context switching.
A few things worth knowing before you set these up:
- Some integrations, including Salesforce, require a helper app to be installed from the Google Workspace Marketplace by you or your admin.
- Each integration requires you to grant permissions to connect Workspace Studio to the third-party service. If a required permission is missing, the relevant step simply will not work.
- When you add variables to integration steps, those variables may contain Google Account data, such as the contents of a Gmail message or a Calendar event. That data will be shared with the third-party service. Google is explicit about this: make sure you trust the service before connecting it.
Outbound webhooks
Webhooks allow a flow to send an HTTP request to an external endpoint, triggering an action in another system. The destination URL must be a full static address (starting with http:// or https://). Variables are not permitted in the URL field, which is a deliberate security constraint. The URL itself is stored securely.
On supported editions (Business Plus, Enterprise Standard, Enterprise Plus, Education Standard, and Education Plus), admins can configure a URL allowlist to restrict which endpoints flows are permitted to contact.
What this means for your organisation
The honest answer is: it depends on what you are already doing.
If your team runs most of its work inside Google Workspace and has been stitching things together with manual processes or third-party automation tools, these features give you a path to consolidate some of that inside Studio, under your existing admin controls and governance framework.
The third-party integrations in particular close a gap that has been frustrating for Workspace-first organisations. Being able to update a Jira ticket, post a Slack message, or log a Salesforce record as part of a flow, without leaving Workspace or maintaining a separate integration platform, reduces friction and the number of tools your IT team needs to manage.
Custom starters are equally valuable for teams that work the other way around: if an event in Salesforce or Jira should kick off a process in Workspace, that is now possible without custom code at the system boundary.
What admins need to do
All four features are disabled by default. To enable them, go to the Admin Console and navigate to Apps > Google Workspace > Workspace Studio. From there you can switch on individual capabilities for your organisation.
Approval controls are managed separately under Apps > Google Workspace > Workspace Studio > Approvals. Custom steps and integrations each have their own approval settings. Webhooks use the approval settings for Sensitive Steps, so if you have already configured those, webhooks will inherit that behaviour.
The admin console controls themselves have a tiered availability. The ability to manage approvals and set URL allowlists requires Enterprise Standard, Enterprise Plus, Teaching and Learning Upgrade, Education Plus, Google AI Pro for Education, or AI Ultra Access. The underlying features are available on a broader set of editions, including Business Starter, Standard, and Plus, and Education Fundamentals.
One additional note: users designated as under 18 cannot use AI features in Workspace Studio.
The bigger picture
This update arrives as part of a sustained push to make Workspace Studio a credible enterprise automation platform. Earlier in 2026, Google added Drive, Gmail, and Chat automation steps, more granular admin controls, and enterprise security features. The addition of custom starters, steps, third-party integrations, and webhooks continues that progression.
It is also worth noting that Google has separately introduced Model Context Protocol (MCP) integrations for Gemini in Workspace, allowing users to interact with services like Asana, HubSpot, and Salesforce directly through Gemini without switching tabs. That capability and Studio flows are complementary: MCP is about conversational access to external data, while flows are about structured, repeatable automation between systems.
If you have not looked at Workspace Studio for a while, now is a reasonable time to revisit it. The platform has moved on considerably from where it started.