Need Help Binding params.result from Listener Bot Response to Wire Field for Dynamic Route Navigation


Hello Team,

I’m using a Call Bot signal in my view which is configured with a listener bot. Inside the listener bot, I’m using runIntegrationAction to call an external integration and fetch data. The bot is returning a response successfully, and I can see the following structure in the Network tab (screenshot attached):

json
Copy
Edit
{
“params”: {
“result”: “01984be0-e0b0-7729-85fb-eb034c00817d”
},
“success”: true
}
Now, I need to use the params.result value from this bot response to dynamically update a wire field, and then pass this value as a parameter (e.g., record_id) into a Route Assignment or navigation flow.

Could you please guide me on:

How to extract params.result from the bot response and bind it to a wire field.

How to ensure that this wire field value is passed as a dynamic parameter in the next screen’s route.

The goal is to enable navigation like /expected?record_id=01984be0-e0b0-7729-85fb-eb034c00817d.

Hello @rbdwt09 -

Is this different from the question you asked in Help with Passing core_id After Form Submission to Display Data in Next View - Q&A - UES.IO – User Experience Studio and if so, could you explain how?

Thanks!

Yes — it’s related, but the intention behind my initial message was specifically to understand how to dynamically set the routing value (like core_id) in the route path itself, not just how to access it in the next view.

In my latest message, I’ve clarified this more directly — I’m trying to pass the dynamic record_id (returned from a bot) into the URL (e.g. /expected?record_id=…) at the time of navigation.I’d like to dynamically populate the “Record ID” field in the Navigate to route assignment signal, as shown in the screenshot below.

@rbdwt09 Seeing as we manage to meet online I am closing this issue.

The result was that the record was not being saved before the redirect and therefore we could not send the record_id ${uesio/core.id} to the new view.

Solved.