--- title: Including variables and other data description: Many of the nodes in a flow can make use of data from outside of the node. This data can include: component: davinci page_id: davinci:flows:davinci_global_variables canonical_url: http://docs.pingidentity.com/davinci/flows/davinci_global_variables.html revdate: June 5, 2025 section_ids: global-variable-reference: Global variable reference --- # Including variables and other data Many of the nodes in a flow can make use of data from outside of the node. This data can include: * **Global variables**: Parameters available throughout the flow. These parameters can come from the flow invocation, the environment, or other sources. - **Node-specific data**: Many nodes create or import data, such as user details, which is then available to future nodes. - **Variable values**: You can include [variable values](../variables/davinci_variables.html) from relevant variable types. To include one or more of these parameters in a node: 1. Create or open a flow. 2. In your flow, select a node, then locate a field that requires data. 3. In the field, click the **{}** icon. ![Screenshot showing the HTML Template field with the \\{} icon in the lower right.](_images/dkb1700084211470.png) 4. In the **Choose Connector** list, select an option: * Select **Global** to add a global variable. * Select **SK-Components** to add an [SK-Component](davinci_sk_components_reference_guide.html). * Select a previous node name to add data from that node. * Select a variable type to add a variable value. The selected category expands to display the available variable or component values. | | | | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | By default, you can only select nodes that precede the current node. If the flow contains loops, you can click **Show All Nodes** to display nodes that appear later in the flow. | 5. Select a value to include. 6. Click **Apply** after you finish adding parameters. ## Global variable reference Global parameters are parameters available throughout the flow. | Parameter | Description | | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `companyId` | The company ID for the environment. | | `flowId` | The ID of the flow. | | `flowVersionId` | The flow version number being run. | | `interactionId` | The ID for the flow execution. | | `policyId` | The ID of the flow policy used to launch the flow. | | `ip` | The end user's IP address.This value is repopulated by the most recent HTTP request. This can include out-of-band continue or webhook nodes that are active on the current branch of the flow, where the client might be different from the one that initiated the flow. | | `userAgent` | The end user's user agent.This value is repopulated by the most recent HTTP request. This can include out-of-band continue or webhook nodes that are active on the current branch of the flow, where the client might be different from the one that initiated the flow. | | `skOpenId` | An object containing authorization request parameters. | | `cookies` | The cookies present in the API request that invoked the flow. | | `origin` | The value of the Origin header. | | `originCookies` | A string used to address the case where the UI the user is interacting with has a different domain than the domain the widget is making API calls to. | | `xDeviceTrust` | A header used by the Chrome Enterprise connector. | | `xVerifiedAccessChallengeResponse` | A header used by the Chrome Enterprise connector. | | `eventTimestamp` | The timestamp at which the most recent node in the flow was executed. For example, `1750864113753`. | | `eventTimestampHumanReadable` | The timestamp at which the most recent node in the flow was executed in human-readable format. For example, `6/25/2025, 3:08:33 PM`. | | `sessionToken` | The value of the session token cookie that PingOne uses to track the authentication session. | | `sessionTokenMaxAge` | A value that controls the expiration of the PingOne session token cookie. | | `p1UserId` | The PingOne User ID for the current user, if it is known. | | `currentRequest > isSdk` | A boolean indicating whether the flow was launched with the SDK. | | `currentRequest > platformType` | A string value indicating which platform invoked the SDK request. | | `currentRequest > connection > ip` | The socket IP address of the connection used to submit the most recent request.Used when a [Cloudflare custom domain has been configured in PingOne](http://docs.pingidentity.com/pingone/settings/p1_set_up_custom_domain.html). | | `currentRequest > connection > verified` | Indicates whether the connection used to submit the most recent request has been verified according to the [inbound traffic criteria in PingOne](http://docs.pingidentity.com/pingone/settings/p1_configure_inbound_traffic_policies.html). If the criteria is **Match All Traffic**, the connection isn't considered verified.Used when a [Cloudflare custom domain has been configured in PingOne](http://docs.pingidentity.com/pingone/settings/p1_set_up_custom_domain.html). | | `currentRequest > connection > id` | The UUID of the inbound traffic policy matched to the request.Used when a [Cloudflare custom domain has been configured in PingOne](http://docs.pingidentity.com/pingone/settings/p1_set_up_custom_domain.html). | | `currentRequest > connection > mtlsThumbprint` | The SHA-256 thumbprint, in lowercase hexadecimal, of the mTLS certificate used by the connection that submitted the most recent request. For standard TLS connections, this value is empty.Used when a [Cloudflare custom domain has been configured in PingOne](http://docs.pingidentity.com/pingone/settings/p1_set_up_custom_domain.html).This variable is used when mTLS is enabled for the custom domain. Learn more in the [API reference documentation](https://apidocs.pingidentity.com/pingone/platform/v1/api/#put-update-domain). | | `currentRequest > connection > headers` | The custom headers submitted with the most recent request.Used when a [Cloudflare custom domain has been configured in PingOne](http://docs.pingidentity.com/pingone/settings/p1_set_up_custom_domain.html). | | `language` | The user's language setting. This value comes from the user's browser language setting unless overridden by the Variables connector. | | `parameters` | An object containing the parameters of the request made to invoke the flow, if the flow has an input schema. | | `userInfo` | An object containing information about the user if the user has been identified. | | `domainPublicHost` | A string containing the custom domain, if one is being used to access DaVinci. | | `authentication` | An object containing the userId and authentication methods fulfilled by a PingOne capability, if any. | | `authentication > userID` | The userID of the user identified by a PingOne authentication event. | | `authentication > methods` | The authentication method used during the PingOne authentication event. This parameter uses RFC8176 values where possible (such as `pwd`, `mfa`, or `sms`.) |