KOKOCAL SCRIPT

Guide

Apps Script Basics Guide

This guide covers the Apps Script basics to know before installing scripts generated by KOKOCAL SCRIPT: pasting, saving, first authorization, triggers, HTML files, and how to think about using multiple scripts.

Published: 2026.08.02Updated: 2026.08.02

Check before pasting

Review required files such as .gs files, HTML files, and the Apps Script project name first.

Understand first authorization

Confirm the meaning of permissions requested by Google's authorization screen before running.

Test safely

Use backups or test files and verify behavior before real operation.

Apps Script basics

What Apps Script is

Apps Script is Google's script runtime for adding custom menus, processes, and automation to Google Sheets, Google Slides, and other files. KOKOCAL SCRIPT generates scripts that you paste into Apps Script.

Bound scripts

Most generators are installed by opening Apps Script from the target spreadsheet or slide file and binding the script to that file. This makes menus and sidebars easy to show inside the file, but setup is needed for each file you want to use.

.gs and HTML files

Paste Apps Script code into the .gs files shown in the generated result, such as KOKOCAL_Menu.gs and KOKOCAL_<ToolName>.gs. Generators with sidebars or UI parts may also require HTML files such as KOKOCAL_SlidesLayerPanelView.html. Create files with the exact names shown in the generated result.

First authorization

The first execution asks for Google account authorization. Allow only after checking the permissions required for reading and writing the target file, showing UI, creating triggers, and other needed operations.

Setup flow

  1. 1

    Open the target file

    Open the Google Sheets, Google Slides, or other file where you want to use the generated script.

  2. 2

    Open Apps Script

    Open Apps Script from the Extensions menu. If existing code is present, back it up before pasting.

  3. 3

    Create required files

    Create KOKOCAL_Menu.gs, KOKOCAL_<ToolName>.gs, and any required HTML files using the exact names shown in the generated result.

  4. 4

    Save and run initial setup

    After saving, run the specified setup function or menu creation function.

  5. 5

    Reload the source file

    For menu-adding scripts, reload the target file so the custom menu appears.

  6. 6

    Run post-install checks

    Follow the review points in the generated result and test with a copied file or backed-up file.

Generated results include a setup guide download. Save it before leaving the page so you can review setup steps, review points, code, and JSON later.

Cautions

Create a backup

Before running scripts that modify data, copy the file and keep a backup. This is especially important for bulk formatting and sync processes.

Check existing KOKOCAL_Menu.gs and triggers

When adding multiple scripts to one project, check KOKOCAL_Menu.gs, registerMenu functions, and triggers for duplicates.

Understand permissions

The authorization screen shows which Google services the script accesses. If unsure, test with a copied file first.

Watch processing volume and runtime

Apps Script has execution time and read/write limits. For large data, keep batch sizes and target ranges modest.

Common issues

Menu does not appear

After running the setup function, reload the target file. KOKOCAL_Menu.gs creates the shared menu from onOpen, so a reload is required.

HTML file is missing

Sidebar-based scripts require HTML files in addition to .gs files. Match the file name, including capitalization, to the generated result.

Authorization stops the process

Depending on your account or organization settings, a warning may appear. Confirm that it is code you generated yourself and run it in a test file first.

Multiple scripts conflict

Check duplicate KOKOCAL_Menu.gs files, registerMenu functions, triggers, and shared function names. See the multiple scripts guide when using several scripts together.