Quick answer: Google Workspace Studio is rolling out custom starters, custom steps, third-party integrations and webhooks. Rapid Release users begin seeing the features on September 21, 2026; Scheduled Release rollout starts September 30. Admins must enable the controls first, so the safest rollout is a small pilot with approved apps, allowed webhook domains, human approval and activity alerts.[1]
This guide explains what changed, where administrators enable it, which Workspace editions are eligible, and how to test one useful automation without exposing Gmail, Chat or Calendar data to an untrusted service.
What is new in Workspace Studio?
| Feature | What it does | Practical example |
|---|---|---|
| Custom starters | Start a Studio flow from a real-time event in another application. | Begin an onboarding flow when an approved HR system creates an employee. |
| Custom steps | Run organization-specific logic, including logic built with Google Apps Script. | Validate a request against an internal policy before continuing. |
| Third-party integrations | Pass information between Workspace and supported outside services. | Create a Jira item or add a Mailchimp contact after an approved event. |
| Webhooks | Send an HTTP request to an external endpoint. | Notify an internal system when a flow reaches a defined stage. |
Google lists Asana, Confluence, HubSpot, Jira, Mailchimp, QuickBooks, Salesforce and Slack among the initial third-party integrations, and labels those integrations as beta in the launch announcement.[1] The user help pages also describe custom steps and integration steps as limited-preview features, so availability may still depend on the account, administrator policy and rollout track.[2][3]
Admin setup checklist
- Choose a pilot group. Start with a small organizational unit or trusted group instead of enabling advanced actions domain-wide.
- Open the controls. In the Admin console, go to Apps → Google Workspace → Workspace Studio.
- Review each control separately. Google says custom steps, integrations and webhooks are off by default. Enable only the capabilities required by the pilot.[1]
- Set approval requirements. Review the Studio Approvals page. Custom steps and integrations have separate approval settings, while webhooks follow the approval policy for sensitive steps.[1]
- Restrict add-ons and integrations. Use the Google Workspace Marketplace allowlist so users can install only reviewed integrations and published custom steps.[5]
- Allowlist webhook destinations where supported. Do not permit arbitrary destinations when a narrower list will work.
- Turn on monitoring. Create alerts for unusually frequent runs and review Workspace Studio log events.
- Test with non-sensitive data. Confirm the payload, destination, approval prompt, error handling and audit trail before using customer or internal business data.
Webhook URL allowlists are available on Business Plus, Enterprise Standard, Enterprise Plus, Education Standard and Education Plus, according to Google’s launch notice.[1] If your edition does not support this control, keep the webhook feature disabled unless the risk can be managed another way.
A safe first webhook test
A webhook is an HTTP request sent to a URL that you specify. Workspace Studio supports a webhook step, and Google recommends JSON when sending structured data. The Activity tab can be used after a run to inspect what the webhook did.[4]
- Create a test endpoint that records only a timestamp, test ID and status.
- Create a Studio flow with a low-risk manual or test starter.
- Add the webhook step and select the required HTTP method.
- Use a minimal JSON payload such as the example below.
- Run the flow once and inspect both the receiving system and Studio’s Activity tab.
- Verify that no email body, Chat message, Calendar description, access token or personal information was included.
- Test a failed request so the team knows how the flow behaves when the destination is unavailable.
- Only then replace the test fields with the minimum production data needed.
{
"event": "studio-pilot-check",
"test_id": "WS-001",
"status": "approved"
}Do not paste secrets into a payload. Google warns that variables used in integrations or add-on steps can contain Google Account data, including Gmail or Chat content and Calendar event information, which may then be shared with the external service.[2][3]
Three useful pilot flows
1. Approved request to Jira
Start with a form or approved Workspace event, require human review, then create a Jira issue containing only the request ID, category and owner. Keep attachments and private message bodies out of the first version.
2. Qualified lead to CRM
After a person confirms that a lead is valid, send the minimum contact fields to HubSpot or Salesforce. Add duplicate checking and a visible consent/source field before automating broader enrichment.
3. Internal status webhook
When an internal approval is complete, send a status code to a company-owned endpoint. This is a good first webhook because the destination and accepted payload can be controlled by the same organization.
Rollout dates and eligible editions
- Admin settings: rollout began September 17, 2026 for Rapid and Scheduled Release domains.
- Rapid Release users: full rollout begins September 21, 2026 and may take one to three days.
- Scheduled Release users: gradual rollout begins September 30, 2026 and may take up to 15 days.
Google lists Business Starter, Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Fundamentals, Education Standard and Education Plus, plus specified Education and AI add-ons, as eligible for the launch.[1] A missing option on the first day does not necessarily mean the edition is unsupported; check the rollout track, administrator policy and Marketplace restrictions.
Limits and operational guardrails
Google’s admin guide currently states that a user can create up to 25 flows, a flow can contain up to 20 steps, and no more than 25 active flows can start from new Gmail messages. It also notes that daily run limits apply.[5]
- Use a named owner and backup owner for every production flow.
- Keep a short record of its trigger, destinations, data fields and business purpose.
- Require approval before sending externally or modifying important records.
- Use a test environment wherever the destination provides one.
- Review failed and unusually frequent runs.
- Document a kill switch before launch.
Google recommends alerting on high-frequency activity and describes an emergency stop method: move the flow owner into an organizational unit where Workspace Studio is disabled, which stops that user’s flows.[5]
Frequently asked questions
Why can’t I see custom steps or webhooks yet?
The feature may still be rolling out, your administrator may not have enabled it, or your organization may restrict the required Marketplace item. Rapid Release rollout starts September 21, while Scheduled Release rollout starts September 30.[1]
Are the new controls enabled automatically?
No. Google says custom steps, integration and webhook settings are off by default in the Admin console.[1]
Which third-party apps are included?
The initial list in Google’s announcement includes Asana, Confluence, HubSpot, Jira, Mailchimp, QuickBooks, Salesforce and Slack.[1]
Can a webhook expose Workspace data?
Yes. If a payload includes variables from Gmail, Chat, Calendar or another step, that data can be sent to the external endpoint. Use trusted destinations, minimum necessary fields, approvals and an allowlist where available.[4]
Should a company enable everything on day one?
No. A controlled pilot is safer: one team, one low-risk flow, one approved destination, monitoring enabled and a documented stop procedure.