The following variables are supported by Lingk for use in your recipes.You can also extend your recipes with Jinja.Variable CollectionExamplePurposeenv{{env.name}}The data coming from an env.dict{{dict.name}}The data coming from an event.var{{var.name}}The data coming from a connector or table.config{{config.name}}The data coming from this connnector's  properties.executionContext*{{executionContext.name}}The data coming from the execution context table.The env Variable CollectionScope: Statements and Connector PropertiesType: StaticThe env Collection provides you with information about the environment that the recipe is running in. This can be helpful for pulling in environment specific values from lookups (file or API) during recipe execution. Available VariablesVariableDescription{{env.name}}The name of the environment. {{env.recipeVersionNumber}}The recipe version number. {{env.recipeVersionId}}The recipe version ID.{{env.recipeId}}The recipe specific ID.The dict Variable CollectionScope: Statements and Connector PropertiesType:  DynamicThe dict collection contains the JSON structure passed in via event-triggered recipe execution. This collection is ideal for parameterizing a recipe to be used in different contexts based on external events.The var Variable CollectionScope: Connector PropertiesType:  DynamicThe var collection contains a tabular dataset resulting from a ParameterizedBy property with REFRESH or from INSERT, UPDATE, or DELETE payloads. Use the Var collection like a "For" loop on a connector to parameterized properties with values from a previous statement. The executionContext Variable CollectionScope: Statements and Connector PropertiesType:  DynamicThe execution context variable collection is now a legacy feature. We recommend, as a security best practice, that you use environment variables for all inline authentication.The executionContext collection contains data inserted into the executionContext table during a statement. By default, executionContext is empty until you perform the following statement:  - statement: INSERT someData INTO executionContextAfter this statement, data is in the  executionContext dataset and accessible in connector properties after a REFRESH statement.executionContext is commonly used for storing an authorization token used in an OAuth flow that impacts multiple connectors during the execution of a recipe. Please use the more secure and recommended environment variables feature to handle inline authentication on Lingk.The config Variable CollectionScope:  Individual Connector PropertiesType:  DynamicThe config collection contains a list of configuration properties on a connector.Here is an example connector that utilizes the config collection of data.-
name: sourceLeadData
type: json
properties:
jsonObject: >
[
{ "leadId": "1", "firstName": "{{config.hello}}", "lastName": "Thomas", "leadScore": 88 },
{ "leadId": "2", "firstName": "Anne", "lastName": "Jacobs", "leadScore": 32 }
]
hello: world