Hi there, my request has a path variable but it doesn’t appear in the Variables section. How to make it work?
Thanks!
Hi @ltvdev
Welcome to the forums!
If you want the request to pull variables from your environment, you can leave the variable blocks blank, they will pull values with the same name from your attached environment.
In the below example, it will pull value from “New Environment”
If you wish to inject a value for the variable from the flow, you can attach it directly and then select the path.
In this example it will use abc to fill value
Let me know if that solves your issue.
Yes, indeed, thank you. I assumed :campaignId in my request in the collection will be automatically translated into a variable in flows. I changed the request as follows and it worked
Hi @flows-daniel
I wonder if you actually read the issue the @ltvdev had or just passed it to AI and copy pasted answer. Because the main issue is that, we build API endpoints like user/:id and create openAPI documentation. Postman collection works fine with that, we can dynamically input path variables. But somehow in postman flows, we cannot pass/edit path variables from collection requests. We need to change collection request url from users/:id to user/{{id}}. And it’s disgusting. It gets out of sync with openapi specs and a lot of troubles.
you called out the issue correct, path variables eg /:id are not recognized as variables in flows. we will look at supporting this, thanks for the feedback.
currently the only workaround is what was described earlier
and can confirm Daniel is 100% not AI.
2 Likes