System variables

system variables 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 you can access the scenario variables under the custom and system variables tab when mapping a value in a module system variables include information about the {{scenario singular lowercase}} itself (scenario id, scenario name, scenario url) the specific {{scenario singular lowercase}} execution (execution id, operations consumed, data consumed, execution start date/time) the team the {{scenario singular lowercase}} is in (team id, team name) the organization the {{scenario singular lowercase}} is in (organization id, organization name, operations left, data left, zone domain) system variables are useful for error handling and {{scenario singular lowercase}} activity tracking for example, if there is an error in your {{scenario singular lowercase}} , you can use the {{scenario singular lowercase}} id or organization name variables to pinpoint the exact {{scenario singular lowercase}} execution and organization in which the error occurred here are some other situations for which you might use system variables create a slack message, email, or support ticket that contains a link to the {{scenario singular lowercase}} execution that created the message set email notifications to notify you once the operations left value reaches a certain number you can also reuse system variables and map them to any module in the module's input fields example get notified before you reach your operations limit in this example, we imagine that at some point in your {{scenario singular lowercase}} you want to notify a team member of the number of operations left in your organization we use a router to send an email when there are 1000 5000 operations left and when there are under 1000 operations left notify a team member based on the number of operations left in your {{scenario singular lowercase}} , add a router in the first route, click the wrench icon to set up a filter label 1000 5000 operations left condition map the condition to the operations left system variable change the operator to numeric operators greater than and enter 1000 in the field click add and rule condition map the second condition to the operations left system variable change the operator to numeric operators less than or equal to and enter 5000 in the field click save after this filter in the first route, add an email > send an email to a team member module and create a connection in the to field, select the member of your team you want to send an email to in the subject field, enter a relevant subject in the content field, enter the text of your email, mapping the operations left variable you can use html tags click save in the second route, click the wrench icon to set up a filter label 1000 or fewer operations left condition map the condition to the operations left system variable change the operator to numeric operators less than or equal to and enter 1000 in the field click save after this filter in the second route, add an email > send an email to a team member module in the to field, select the member of your team you want to send an email to in the subject field, enter a relevant subject in the content field, enter the text of your email, mapping the operations left variable you can use html tags click save as the number of operations left drops to the filtered amounts, your team member receives email notifications