💡 Platform feature: Workspace Studio custom-steps bridge (expose script catalog as Studio flow actions)

[github-actions[bot]]

Summary

Package the existing script catalog (gmail-to-drive-by-labels, calendar-to-sheets, calendar-to-briefing-doc) as Workspace Studio custom steps and starters, enabling non-technical users to discover and compose these automations inside Google's native no-code flow builder rather than only through the deploy page.

Market Signal

Google launched Workspace Studio custom starters, custom steps, third-party integrations, and webhooks on September 17–21, 2026. Custom steps explicitly use Apps Script functions — the announcement states users can "seamlessly connect custom Google Apps Script functions" within Studio flows. This creates a native distribution channel reaching every Business, Enterprise, and Education Workspace plan user. Eight third-party integrations (Asana, Confluence, HubSpot, Jira, Mailchimp, QuickBooks, Salesforce, Slack) launched alongside, signaling Google's commitment to Studio as a central automation hub.

Note: This is distinct from Discussion #537 (Workspace Studio Skills packaging). Skills are reusable atomic automation assets; custom steps/starters are the mechanism for integrating Apps Script functions into Studio flows as drag-and-drop components. Both are complementary, but this proposal targets the just-launched custom steps API specifically.

User Signal

• The deploy page PRD identifies that "adoption dies at configuration." Studio's flow builder eliminates that barrier entirely by exposing scripts as drag-and-drop steps with built-in input forms
• Discussion 💡 Platform feature: Workspace Studio Skills packaging for script catalog #537 proposed Skills packaging; Discussion 💡 Platform feature: deploy-page MCP gateway for Gemini Spark automation #559 proposed an MCP gateway — neither addresses the custom steps/starters API
• Apps Script becoming a core Workspace service (June 2026) with data regions support (September 2026) legitimizes building on this foundation

Technical Opportunity

getScriptCatalog() in src/deploy/index.js already defines the catalog with IDs, descriptions, files, and scopes. Each script's code.gs exports entry-point functions. The bridge would create thin wrapper functions conforming to Studio's custom step contract, mapping Studio inputs to config.gs parameters. The existing testable architecture (extract to src/index.js, inject GAS services) makes each script's logic naturally composable as Studio steps.

Assessment

Dimension	Score	Rationale
Feasibility	high	Custom steps use standard Apps Script functions — the same foundation this project already builds on. The catalog and entry points already exist.
Impact	high	Opens the suite to the entire Workspace Studio user base across all supported editions. Positions the project as a go-to source for pre-built Studio steps.
Urgency	high	Custom steps launched this week (Sept 17–21). First-mover advantage for open-source GAS projects providing ready-made Studio steps.

Adversarial Review

Strongest objection: Studio's custom steps API is brand new and could change rapidly. Building against an unstable API risks wasted effort and maintenance burden.
Rebuttal: The API uses standard Apps Script functions — the same foundation this project already builds on. The risk is in the Studio-specific packaging, not the core script logic. Starting with a single script as a POC (calendar-to-sheets is simplest) limits exposure while establishing first-mover position. Being early in the ecosystem means the project gets cited in tutorials, community examples, and Google's own documentation.

Suggested Next Step

Create a POC wrapping calendar-to-sheets as a Workspace Studio custom step. Document the custom step contract and input/output mapping. Test with a Studio flow end-to-end. If successful, extend to all catalog scripts and publish a setup guide.

[github-actions[bot]]

Weekly Update

What Changed

Workspace Studio custom starters + steps went GA on September 21, 2026 — this idea is now immediately implementable. Key new signals:

• GA announcement: Automate workflows with custom starters and steps, third-party integrations, and webhooks in Workspace Studio (Sep 21, 2026)
• Availability: Business Starter/Standard/Plus, Enterprise Standard/Plus, Education editions — covers the project's target audience
• Implementation path: Each custom step requires two Apps Script callbacks: onConfigFunction (renders config card) and onExecuteFunction (receives inputs, runs logic, returns outputs). The project's existing config.gs + src/index.js separation maps directly to this pattern.
• Quickstart available: Build a calculator step with Apps Script provides a working reference implementation
• AppSheet example on GitHub: mhawksey/appsheet-custom-studio-step-example — shows how to read/update AppSheet apps via custom steps
• Custom starters can also trigger flows from external events, enabling the webhook receiver pattern
• Admin note: Custom steps are OFF by default in Workspace admin settings — users with individual/small-team Workspace accounts can toggle this on themselves

Updated Assessment

Dimension	Previous	Current	Delta
Feasibility	med	high	↑ API is GA with quickstart guide and example code
Impact	high	high	→ Unchanged — audience multiplier effect remains strong
Urgency	med	high	↑ GA creates a first-mover window; competitors will build Studio integrations

Recommendation

Advance — This idea should move to implementation planning. Suggested first step: wrap calendar-to-sheets as a proof-of-concept Studio custom step using the quickstart pattern. This validates the wrapper approach with the simplest existing script before scaling to the full catalog.