Skip to main content
“Me” values are a special category of value that automatically resolve to information about the currently authenticated user — the person running the journey. Instead of asking each user to enter their own email, user ID, or display name, you reference the “me” value for that field and Reqflo resolves it from their session.

​
When to use it

Use “me” values when:
  • A step needs to be scoped to the user running the journey (for example, “get my account”, “create a resource owned by me”, “send a notification to my email”).
  • You are building a Runbook and want each support agent who runs it to automatically act as themselves.
  • You want to avoid sharing a generic test account and instead have each user exercise the API as their own identity.
“Me” values make journeys feel personal and contextual without requiring each user to configure their own run inputs.

​
Key concepts

Resolved from the authenticated session. When a journey runs, Reqflo reads “me” values from the identity of the authenticated user. No manual entry is required. Available “me” fields. The exact fields available depend on what Reqflo stores about the authenticated user. Common examples include:
FieldResolves to
me.emailThe authenticated user’s email address
me.user_idThe authenticated user’s internal user ID
me.nameThe authenticated user’s display name
The full list of available “me” fields depends on your organization’s Reqflo configuration. Check the Values panel to see which “me” fields are available in your workspace.
Per-user, not per-journey. Because “me” values resolve from the runner’s identity, the same journey produces different values for different users. This is intentional — it is what makes “me” values useful for identity-scoped testing. Cloud Runner behavior. When a journey runs via the Cloud Runner (for example, in CI), there may not be an interactive user session. In that context, “me” values resolve from the service account or runner identity configured for that run. Check your runner configuration if you need a specific identity in automated runs.

​
How it works

1

Reference a 'me' value in a step

In the step’s value configuration, select “me” as the source and choose the field (for example, me.email). You can also reference it directly in YAML.
2

Run the journey

When the journey runs, Reqflo resolves the “me” value from the current user’s authenticated session. The resolved value is used in the request just like any other value.

​
Examples

Referencing a “me” value in YAML: 
steps:
  - name: Get my account
    request: get-account
    values:
      email: ${{ me.email }}

  - name: Create my resource
    request: create-resource
    values:
      ownerId: ${{ me.user_id }}
      ownerName: ${{ me.name }}
In a Runbook context: A support agent runs a Runbook to investigate a customer issue. The Runbook uses me.email in an audit-log step so the log records which agent ran the investigation — automatically, without the agent needing to type their own email. Combining with run inputs: 
steps:
  - name: Transfer funds
    request: transfer-funds
    values:
      fromUserId: ${{ me.user_id }}
      toUserId: ${{ run.recipient_id }}
      amount: ${{ run.amount }}
Here fromUserId is always the running user, while recipient_id and amount are supplied as run inputs.