Flows API
  • Globus Flows
  • Overview
  • Authentication and Authorization
  • Authoring flows
    • Introduction
    • Actions
    • Expressions
    • Protecting Secrets
    • Handling Exceptions
    • Performing Actions as Different Users
    • Run Context
    • Example Flows
  • Authoring Input Schemas
  • Scopes, Consents, and Resuming Runs
  • Permissions
  • Limits
  • Hosted Action Providers
    • Hello World
    • Globus Transfer - Transfer Task
    • Globus Transfer - Delete Task
    • Globus Transfer - Set Permission
    • Globus Transfer - List Directory Contents
    • Globus Transfer - Make Directory
    • Globus Transfer - Get Collection
    • Globus Search - Ingest Task
    • Globus Search - Delete Task
    • Send Notification Email
    • Wait For User Selection
    • Expression Evaluation
    • Datacite Mint
Skip to main content
Globus Docs
  • APIs
    Auth Flows Groups Search Transfer Globus Connect Server Compute Helper Pages
  • Applications
    Globus Connect Personal Globus Connect Server Premium Storage Connectors Compute Command Line Interface Python SDK JavaScript SDK
  • Guides
  • Support
    FAQs Mailing Lists Contact Us Check Support Tickets
  1. Home
  2. Globus Services
  3. Globus Flows
  4. Authoring flows
  5. Run Context

Run Context

Basic information about the flow’s state and the user invoking the flow is provided through a "virtual", read-only property available at the JSONPath $._context. This path may be used in a path for a Parameters value on an action or Pass state type, or in expressions which are evaluated when generating Parameters values as described above. This allows the flow to use these values as necessary for passing into actions as parameters. As this is a read-only value, the _context cannot be overwritten by using the path in a ResultPath on any state. The _context value is itself an object containing the following properties:

Property name

Description

flow_id

The id of the flow that is executing

run_id

The unique id assigned to this execution of the flow

username

The Globus Auth username for the user invoking the flow

email

The email address for the user invoking the flow

user_id

The Globus Auth user id for the user invoking the flow (in URN format)

identities

A list of all identities associated with the user invoking the flow (in URN format)

token_info

A child object containing the fields exp, iat, and nbf (described below)

The token_info fields are defined as follows:

  • exp: Timestamp, measured in the number of seconds since UTC January 1, 1970, indicating when this token will expire.

  • iat: Timestamp, measured in the number of seconds since UTC January 1, 1970, indicating when this token was originally issued.

  • nbf: Timestamp, measured in the number of seconds since UTC January 1, 1970, indicating when this token is not to be used before.

  • Globus Flows
  • Overview
  • Authentication and Authorization
  • Authoring flows
    • Introduction
    • Actions
    • Expressions
    • Protecting Secrets
    • Handling Exceptions
    • Performing Actions as Different Users
    • Run Context
    • Example Flows
  • Authoring Input Schemas
  • Scopes, Consents, and Resuming Runs
  • Permissions
  • Limits
  • Hosted Action Providers
    • Hello World
    • Globus Transfer - Transfer Task
    • Globus Transfer - Delete Task
    • Globus Transfer - Set Permission
    • Globus Transfer - List Directory Contents
    • Globus Transfer - Make Directory
    • Globus Transfer - Get Collection
    • Globus Search - Ingest Task
    • Globus Search - Delete Task
    • Send Notification Email
    • Wait For User Selection
    • Expression Evaluation
    • Datacite Mint
© 2010- The University of Chicago Legal Privacy Accessibility Feedback