Script Engine is the page in Workspace Administration where workspace administrators create, schedule and monitor the JavaScript scripts that run in their workspace. From one place you can see every script, write and edit code in a built-in editor, set memory and timeout limits, choose which workspace secrets each script can use, and review every run.

Scripts that sync data, call external services or keep records current need a home where administrators can see what exists, when it runs and whether it worked. Script Engine is that home. Use it to:

Secrets are managed on their own page. In the left sidebar, open Workspace Administration and select Secrets, directly below Script Engine. For details, see Secrets Management.

Note: You can only choose secrets that already exist. To add a new one, create it on the Secrets page first. To read a secret's value in your code, see Using secrets in scripts.

Every script needs a Script ID that is:

For example, nightly-evidence-sync is valid, while Nightly_Sync is not.

After you save a script, it is validated. Each script shows a status badge:

A script can run on a preset schedule or a custom expression. In the script list, the Schedule column shows:

The top of the Script Engine page shows three counts:

Click any count to filter the list to the matching scripts.

Note: Column choices are saved in your browser. If you open Script Engine in a different browser, you will see the default columns.

The list loads in pages. Click Load more at the bottom to see additional scripts.

Export the script list as a CSV file, an Excel (.xlsx) file or a Google Sheet.

Open a script to update its code, settings, schedule, Memory and Timeout limits, or selected secrets. The script is validated again when you save.

Duplicate a script to use it as the starting point for a new one. Before you can save the copy, give it a new, unique Script ID.

Export a script's full definition as a JSON file. The export includes references to the secrets the script uses, but never the secret values themselves.

Every time a script runs, Script Engine records the run. Open a script's run history to review past runs, including each run's execution mode and the script version that ran. Filter and sort the history to find specific runs, and select a run to see its details.

Scenario: Your compliance team needs control evidence pulled from an external system every night, and auditors want proof that each collection ran.

Solution: Create a script that calls the external service, using a secret for its API key, and give it a Daily schedule. Each morning, the script's run history shows whether the collection succeeded.

Scenario: A service desk integration stopped updating tickets, and you are not sure which script is responsible.

Solution: Click the failed-runs count at the top of Script Engine to filter to scripts with recent failures, then open the script's run history to investigate.

Scenario: You want to try a change without affecting a script that is already in use.

Solution: Duplicate the script, give the copy a new Script ID and make your changes there. Once the copy works as expected, update the original.

Scenario: An API key used by several scripts is being replaced.

Solution: Update the value on the Secrets page. Every script that uses that secret picks up the new value automatically, with no script edits needed.

Workspace Administrators on the Enterprise plan or higher.

Secrets moved to their own page in Workspace Administration, directly below Script Engine. Scripts now choose secrets by reference with Choose secrets. See Secrets Management.

No. A JSON export includes references to the secrets a script uses, never their values.

Column choices are saved in your browser, so a different browser or device starts with the default columns.

Last verified: 22 Oct 2026, against the original draft of this article, the Script Engine requirements and the Secrets Management article. No product change was verified in the app in this pass.