Accessing external userId from generate-signed-access-url inside a workflow — which variable?

MindStudio Community Discussion
1

Hi folks,

I am embedding a MindStudio agent via signed access URLs into our React app, and I need the workflow’s HTTP Request block to fetch user-specific data from our own backend.

Our backend calls generate-signed-access-url passing our internal userId (e.g. tb-user-abc123). The signed URL gets embedded in an iframe. When the workflow starts, an HTTP Request block calls our backend endpoint to fetch the session data for that specific user. The backend needs to know which user is asking so it can look up the right data in our database.

I confirmed separately that when I call generate-signed-access-url with userId: "tendbe-test-abc123", the API correctly returns that same value in the response body, so MindStudio is storing it against the managed user record. It just does not appear to surface it to the workflow runtime through any variable syntax I have found.

So the question is , when I call generate-signed-access-url passing an external userId, is there a workflow variable that exposes that exact value at runtime so an HTTP Request block can pass it to an external API? Or is there a recommended pattern for fetching user-specific external data inside a signed-URL-triggered workflow?

thanks!

Manu

2

Hi @Manuel,

Thanks for the post!

There’s currently no workflow variable that exposes the external userId you pass to generate-signed-access-url. The recommended workaround is to append it as a URL query parameter before loading the signed URL:

  1. Add Launch Variables in the Start block (e.g., userID)
  2. Call the API and get the signed URL back
  3. Append your variables to it before loading it: returnedUrl&userID=YourUserID
  4. Use that final URL as your iframe src

The query parameters will then be accessible inside the workflow as variables.