Installable Triggers

Like simple triggers, installable triggers let Apps Script run a function automatically when a certain event, such as opening a document, occurs. Installable triggers, however, offer more flexibility than simple triggers: they can call services that require authorization, they offer several additional types of events including time-driven (clock) triggers, and they can be controlled programmatically. For both simple and installable triggers, Apps Script passes the triggered function an event object that contains information about the context in which the event occurred.

Note: For information on how to use installable triggers in add-on projects, see Add-on triggers.

Restrictions

Even though installable triggers offer more flexibility than simple triggers, they are still subject to several restrictions:

• They don't run if a file is opened in read-only (view or comment) mode. For standalone scripts, users need at least view access to the script file in order for triggers to run properly.

• Script executions and API requests do not cause triggers to run. For example, calling FormResponse.submit() to submit a new form response does not cause the form's submit trigger to run.

  Note: An exception to this restriction is Form.submitGrades(). If your code uses an onFormSubmit trigger, calling Form.submitGrades() triggers the onFormSubmit condition and causes an infinite loop. To prevent the infinite loop, add code that checks whether grades already exist before calling submitGrades().

• Installable triggers always run under the account of the person who created them. For example, if you create an installable open trigger, it runs when your colleague opens the document (if your colleague has edit access), but it runs as your account. This means that if you create a trigger to send an email when a document is opened, the email is always sent from your account, not necessarily the account that opened the document. However, you could create an installable trigger for each account, which would result in one email sent from each account.

• A given account cannot see triggers installed from a second account, even though the first account can still activate those triggers.

• Installable triggers are subject to Apps Script trigger quota limits.

Time-driven triggers

A time-driven trigger (also called a clock trigger) is similar to a cron job in Unix. Time-driven triggers let scripts execute at a particular time or on a recurring interval, as frequently as every minute or as infrequently as once per month. (Note that an add-on can use a time-driven trigger once per hour at most.) The time may be slightly randomized — for example, if you create a recurring 9 a.m. trigger, Apps Script chooses a time between 9 a.m. and 10 a.m., then keeps that timing consistent from day to day so that 24 hours elapse before the trigger fires again.

Event-driven triggers

Installable event-driven triggers are conceptually similar to simple triggers like onOpen(), but they can respond to additional events, and they behave differently.

For example, the installable open trigger for Google Sheets activates whenever the spreadsheet is opened by any user who has edit access, just like the simple onOpen() trigger. However, the installable version can call services that require authorization. The installable version runs with the authorization of the user who created the trigger, even if another user with edit access opens the spreadsheet.

There are several installable triggers for Google Workspace applications:

• An installable open trigger runs when a user opens a spreadsheet, document, or form that they have permission to edit.
• An installable edit trigger runs when a user modifies a value in a spreadsheet.
• An installable change trigger runs when a user modifies the structure of a spreadsheet itself—for example, by adding a new sheet or removing a column.
• An installable form submit trigger runs when a user responds to a form. There are two versions of the form-submit trigger, one for Google Forms itself and one for Sheets if the form submits to a spreadsheet.
• An installable calendar event trigger runs when a user's calendar events are updated—created, edited, or deleted.

You can use installable triggers in standalone and bound scripts. For example, a standalone script can programmatically create an installable trigger for an arbitrary Google Sheets file by calling TriggerBuilder.forSpreadsheet(key) and passing in the spreadsheet's ID.

Managing triggers manually

To manually create an installable trigger in the script editor, follow these steps:

New editor

1. Open your Apps Script project.
2. At the left, click Triggers .
3. At the bottom right, click Add Trigger.
4. Select and configure the type of trigger you want to create.
5. Click Save.

Legacy editor

1. From the script editor, choose Edit > Current project's triggers.
2. Click the link that says: No triggers set up. Click here to add one now.
3. Under Run, select the name of function you want to trigger.
4. Under Events, select either Time-driven or the Google App that the script is bound to (for example, From spreadsheet).
5. Select and configure the type of trigger you want to create (for example, an Hour timer that runs Every hour or an On open trigger).
6. Optionally, click Notifications to configure how and when you are contacted by email if your triggered function fails.
7. Click Save.

Managing triggers programmatically

You can also create and delete triggers programmatically with the Script service. Start by calling ScriptApp.newTrigger(functionName), which returns a TriggerBuilder.

The following example shows how to create two time-driven triggers—one that fires every 6 hours, and one that fires every Monday at 9 a.m. (in the time zone that your script is set to).

triggers/triggers.gs

View on GitHub

/**
 * Creates two time-driven triggers.
 */
function createTimeDrivenTriggers() {
  // Trigger every 6 hours.
  ScriptApp.newTrigger('myFunction')
      .timeBased()
      .everyHours(6)
      .create();

  // Trigger every Monday at 09:00.
  ScriptApp.newTrigger('myFunction')
      .timeBased()
      .onWeekDay(ScriptApp.WeekDay.MONDAY)
      .atHour(9)
      .create();
}

This next example shows how to create an installable open trigger for a spreadsheet. Note that, unlike for a simple onOpen() trigger, the script for the installable trigger does not need to be bound to the spreadsheet. To create this trigger from a standalone script, simply replace SpreadsheetApp.getActive() with a call to SpreadsheetApp.openById(id).

triggers/triggers.gs

View on GitHub

/**
 * Creates a trigger for when a spreadsheet opens.
 */
function createSpreadsheetOpenTrigger() {
  var ss = SpreadsheetApp.getActive();
  ScriptApp.newTrigger('myFunction')
      .forSpreadsheet(ss)
      .onOpen()
      .create();
}

To programmatically modify an existing installable trigger, you must delete it and create a new one. If you have previously stored the ID of a trigger, you can delete it by passing the ID as an argument to the function below.

triggers/triggers.gs

View on GitHub

/**
 * Deletes a trigger.
 * @param {string} triggerId The Trigger ID.
 */
function deleteTrigger(triggerId) {
  // Loop over all triggers.
  var allTriggers = ScriptApp.getProjectTriggers();
  for (var i = 0; i < allTriggers.length; i++) {
    // If the current trigger is the correct one, delete it.
    if (allTriggers[i].getUniqueId() === triggerId) {
      ScriptApp.deleteTrigger(allTriggers[i]);
      break;
    }
  }
}

Errors in triggers

When an installable trigger fires but the function throws an exception or otherwise fails to run successfully, you don't see an error message on your screen. After all, when a time-driven trigger runs or another user activates your form-submit trigger, you might not even be at your computer.

Instead, Apps Script sends you an email like the following:

From: [e-mail]
Subject: Summary of failures for Google Apps Script
Your script has recently failed to finish successfully.
A summary of the failure(s) is shown below.

The email includes a link to deactivate or reconfigure the trigger. If the script is bound to a Google Sheets, Docs, or Forms file, the email also includes a link to that file. These links let you deactivate the trigger or edit the script to fix the bug.

Note: Installable triggers created by add-ons don't send users these email notices.

To review all of the triggers that are associated with your Google account and deactivate the triggers you no longer need, follow these steps:

New editor

1. Go to script.google.com.
2. At the left, click My Triggers.

3. To delete a trigger, at the right of the trigger, click More > Delete trigger.

   Note: Simple triggers like onOpen() can't be deactivated from this page; instead, you must edit the appropriate script and remove or rename the onOpen() function.

Legacy editor

1. Open the script editor by opening any script or visiting script.google.com.
2. Click Edit > All your triggers. If you just created a new script, the script editor prompts you to give the script a name first.
3. A dialog lists every simple or installable trigger that is associated with your account. From this dialog, it is not possible to determine which script uses a given trigger, but if you recognize the function name for an installable trigger and know that you don't need the trigger anymore, you can delete the trigger by clicking the X icon to the left of the function name. Simple triggers like onOpen() cannot be deactivated from this dialog; instead, you must edit the appropriate script and remove or rename the onOpen() function.

Installable triggers in add-ons

For more information on using installable triggers in add-ons, see Add-on triggers.