Variables

variables are containers for storing data you can think of a variable as a “box” for data, with a uniquely named sticker on it imagine you are moving to a new home and you need to pack up all the things in your house you might want a box for clothes, one for books, and one for the dishes when you pack the boxes, it's helpful to add a label to each box that way, you know what is inside variables store data as boxes store items however, unlike a box, you can store only one thing in a variable variables have a fixed name and a value that can change you can reference the name in your {{scenario singular lowercase}} the name is then replaced by the current value of your variable when the {{scenario singular lowercase}} executes when using {{product name}} , you might need to save certain pieces of information and assign a label to the information so that you can retrieve it later a username, the day of the week, or available inventory left in your e shop these are just some examples of data that can be stored in variables as reusable elements that can be mapped to any module in the module's input fields {{product name}} offers four types of variables system variables docid\ ozgahlbj3zkaokwcwayii are provided by {{product name}} you can’t modify or delete system variables they can be used in modules with input fields, filters within the {{scenario singular lowercase}} editor, and in templates scenario variables docid\ xheaxlxyife v0osuxxpe are created within a {{scenario singular lowercase}} for use in {{scenario singular lowercase}} executions you can use the tools docid\ cwfbo7bvo3bpzcsxcaqof and tools docid\ cwfbo7bvo3bpzcsxcaqof tools to define these variables custom variables docid\ xjlokkg ajn437ou5eyn1 are similar to scenario variables, but they are created at the organization or team level and can be accessed and modified within a {{scenario singular lowercase}} execution custom variables are only available with pro, teams, and enterprise pricing plans https //www make com/en/pricing incremental variables docid\ wawi8huolu6xec o1ljys are created for each {{scenario singular lowercase}} you can increment them any time in a {{scenario singular lowercase}} execution the value of the incremental variable can be kept within multiple {{scenario singular lowercase}} executions variable type scope/visibility created modified deleted system variables in all {{scenario plural lowercase}} visability varies (global, team, current {{scenario singular lowercase}} ) by {{product name}} by {{product name}} never deleted scenario variables only in the current {{scenario singular lowercase}} execution only in the {{scenario singular lowercase}} only in the {{scenario singular lowercase}} can’t be deleted, but they no longer exist when the {{scenario singular lowercase}} stops custom variables organization level variables are visible for all scenarios in the organization team level variables are only visible in {{scenario plural lowercase}} built within that team by the admin of the organization or team by the admin of the organization or team within a {{scenario singular lowercase}} , by using the {{product name}} api or the update a custom variable module by the admin of the organization or team incrementable variable in the current {{scenario singular lowercase}} by {{product name}} incremented in the {{scenario singular lowercase}} , using the tool>increment function module value resets for each {{scenario singular lowercase}} execution, or never resets, based on the parameters chosen in the tool>increment function module