---
title: Script variables
description: The variables available to a script depend on several factors:
component: pingidm
version: 8.1
page_id: pingidm:scripting-guide:script-vars
canonical_url: https://docs.pingidentity.com/pingidm/8.1/scripting-guide/script-vars.html
keywords: ["Scripting", "Variables", "Managed Object", "Mappings"]
---

# Script variables

|   |                                                                                                                          |
| - | ------------------------------------------------------------------------------------------------------------------------ |
|   | For more information about the variables available in script triggers, refer to [Script triggers](script-triggers.html). |

The variables available to a script depend on several factors:

* The trigger that launches the script.

* The configuration file in which that trigger is defined.

* The object type:

  * For objects defined in the managed object configuration *(tooltip: You can edit the managed object configuration over REST at the config/managed endpoint, or directly in the conf/managed.json file.)*, the object type is either a managed object, or a managed object property.

  * For objects defined in the mapping configuration *(tooltip: You can manage the mapping configuration over REST at the config/sync endpoint, directly in the conf/sync.json file, or in individual conf/mapping-\<mappingName>.json files.)*, the object can be an object-mapping object, a property object, or a policy object. For more information, refer to [Policy Objects](../synchronization-guide/synchronization-ref.html#sync-policy-objects)).

The following subtopics list the variables available to scripts, based on the configuration file in which the trigger is defined.