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 the name is then replaced by the current value of your variable when the executes when using , 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 types of variables offers four types of variables docid\ ozgahlbj3zkaokwcwayii provided by you can’t modify or delete system variables they can be used in modules with input fields, filters within the editor, and in templates docid\ xheaxlxyife v0osuxxpe c reated within a for use in executions you can use the docid\ cwfbo7bvo3bpzcsxcaqof and docid\ cwfbo7bvo3bpzcsxcaqof tools to define these variables docid\ xjlokkg ajn437ou5eyn1 s imilar to scenario variables, but created at the organization or team level and can be accessed and modified within a execution only available with pro, teams, and enterprise https //www make com/en/pricing docid\ wawi8huolu6xec o1ljys c reated for each you can increment them any time in a execution the value of the incremental variable can be kept within multiple executions variable use cases consider the following examples to determine the best variable to use in your get information use system variable a system variable is available in all , created by , and never deleted share a value between multiple use custom variable organization level custom variables are visible for all scenarios in the organization team level custom variables are only visible in built within that team they can be created, modified, or deleted b y the admin of the organization or team custom variables can also be modified w ithin a , by using the api or the update a custom variable module store a counter that can be shared between multiple runs use custom variable incremental variable an incremental variable is only available in the current incremental variables are created by and are incremented using the tool>increment function module the value resets for each execution, or never resets, based on the parameters chosen in the tool>increment function module set a variable and retrieve its value in the same run use custom variable, with restrictions incremental variable, with restrictions scenario variable variables only exist in the current they can't be deleted, but they no longer exist when the stops running restrictions while you can set the value of a custom variable in a , the other modules will still use its previous value the new value of a custom variable is retrieved only when the starts again the increment is only a counter; you can't store any complex data set a variable and retrieve its value in other use custom variable, with restrictions restriction the value of the variable is retrieved only when the starts its execution if a team or organization variable is modified while a is running, the current run will use the previous value of this variable the new value of a custom variable is retrieved only when the starts again