Before you start

Four things to know before your first session, in the order you'll meet them.

A current browser

Chrome or Edge 80, Firefox 113 or Safari 16.4, or newer.

A Google account

Personal or Google Workspace. With a personal account, the node menu hides the nodes that need Workspace.

  1. If Google opens ScriptGlyph under the wrong account

    If you're signed into several Google accounts, Google may open ScriptGlyph under a different account. Try a separate browser profile or a private window signed into the account you want to use.

    A browser profile

    Best if you'll use ScriptGlyph often.

    A private window

    Quickest for a first look. Sign in to just that account.

  2. Switch on the Apps Script API

    ScriptGlyph writes your automations into your account through this setting. It's off by default, and only you can switch it on.

    1. Open Apps Script settings.
    2. Select Google Apps Script API.
    3. Switch it on. If it already says On, there's nothing to do.
    Open Apps Script settings

    If your organisation blocks it, ask your Google Workspace admin to allow the Apps Script API for you.

  3. Open ScriptGlyph

    Use the link in your invitation. The first time it opens, Google asks you to allow the permissions ScriptGlyph asks for when you open it.

    "Google hasn't verified this app" Expected during the beta, while Google reviews ScriptGlyph. Choose Advanced, then Go to ScriptGlyph (unsafe).
    The permissions ScriptGlyph asks for when you open it
    Google asks to What ScriptGlyph uses it for
    Create and update Google Apps Script projects Writing the automation you built into a project in your account
    Create and update Google Apps Script deployments Publishing the web apps and Chat apps you build
    View Google Apps Script processes The Runs tab: whether a trigger fired, and why a run failed
    Connect to an external service Calling Google's own APIs; nothing goes anywhere else
    Display and run third-party web content in prompts and sidebars inside Google applications Opening the editor inside Sheets, Docs, Slides and Forms
    Only the specific Drive files that you use with this app Saving your projects in your Drive, and opening files you pick
    See your primary Google Account email address Showing who is signed in
    Spreadsheets that this application has been installed in Attaching a new script to the spreadsheet you opened it from
    Documents that this application has been installed in The same, for documents
    Presentations that this application is installed in The same, for presentations
    Forms that this application has been installed in The same, for forms
  4. Your first deploy

    Review and deploy lists the files it will write and the permissions your generated automation needs. Google asks for those when the automation first runs.

    Review and deploy Files
    • Config.gs
    • Main.gs
    • appsscript.json (manifest)
    When the script runs, it will ask permission to
    • See and edit the spreadsheet this script is attached to
    CancelDeploy

    The list differs for every automation. Recreated from ScriptGlyph using sample data.

If something goes wrong

Google's messages are quoted exactly, so you can match the words on your screen.

"Sorry, unable to open the file at present"

Google opened ScriptGlyph under a different account. Go back to step 1.

"This browser cannot run the editor"

The browser is too old. Update it, or use a current Chrome, Edge, Firefox or Safari.

"User has not enabled the Apps Script API"

Step 2 isn't done, or hasn't taken effect yet. Switch it on and try again in a minute.