Hey guys — I’m trying to pass some additional data that can be used later in the login flow. Right now, I’m using the

client

property on the Descope component in the Next.js SDK for this. Is this the right approach for passing custom variables through the flow? Also, what’s the correct way to access this data inside the flow?

Yeah, you can use the client prop on the Descope component for passing data. Pass data in the component:

<Descope
  flowId="my-flow-id"
  client={{ version: "1.2.0", planTier: "pro" }}
/>

@Bhagwanta Yeole Following your example, how would I be able to retrieve this

version

and

planTier

variables on the login flow?

@Akash Jivane @Bhagwanta Yeole can you follow up here

@Gabriel Where do you want to use this variable excatly in the flow or screens?

@Bhagwanta Yeole I want do get the variable and use it in a connector at some point of the login flow.

Okay, let me check.

Hi @Gabriel The reason

{{client.planTier}}

isn't working is that the

client

prop is intended for browser/environment metadata (like browser name/version) and isn't available as a dynamic key inside flows or connectors. To pass custom data like

planTier

and

version

into a connector, you should use the

form

prop instead:

<Descope
  flowId="your-flow-id"
  form={{
    'planTier': 'pro',
    'version': '1.2.0'
  }}
/>

Then in your connector inside the flow, reference it as:

{{form.planTier}}

and

{{form.version}}

The

form

inputs are fully accessible in flow actions, connectors, and conditionals. Doc: https://docs.descope.com/flows/dynamic-keys/flow-inputs

Let me try with the form prop! Thanks @Rahul Rijhwani

Yes please share flow json here

resident-login-copy.json

Looked through the flow JSON, found two issues: 1. ScriptletFailure — TDZ bug in "Get user email" (Task 18) The crash at

1:67

is caused by this line in your scriptlet:

const userEmail = formEmail || unauthUserEmail || userEmail

You're re-declaring

userEmail

with

const

while also referencing it on the right side. JavaScript's

const

creates a Temporal Dead Zone, so

|| userEmail

hits the TDZ of the new variable instead of the scriptArg — causing the

ReferenceError

. Fix it by renaming the const:

const resolvedEmail = formEmail || unauthUserEmail || userEmail
return { userEmail: resolvedEmail };

2.

env

scriptArg is mapped to wrong context key Your

env

arg is mapped to context

"env"

which doesn't exist as a Descope dynamic key — it's always

undefined

. Change it to

form.env

in the scriptlet args. Then pass it from your app:

<Descope form={{ clientId: 1004, env: 'production' }} />

And in the dashboard configure panel, set

env

→

descopeDashboard

to test that branch. The

form.clientId

value itself IS flowing through correctly — the scriptlet crash was just preventing it from being used.

Let's check here. Thanks again!

Did you do above change in flows can you send me your updated flows

here it go

Hey @Gabriel , Can you please try to add curly braces to the variable you want to use from the form or client prop? Attaching the screenshot for your reference.

I tried adding the curly braces before, and now after your suggestion, and it didn't work :(

Let me check with internal team CC @Nick Rodriguez

I was able to fix this issue!

Great, Let us know if any other help needed.

I tried with form.customerId and it worked on both the descope dashboard and inside my next.js app

Sounds good now it is working Thanks for highlight, We will add this point in to document