Unable to send integer query key value on a HTTP request

(0) Share

Report

Posted on by special-analyst

Hi, guys!

How are you?

I'm facing a problem that seems to be a bug. I cannot send an integer as a query key value on a HTTP request. When the flow runs, the integer value is automatically converted to a string, doesn't matter what I do. I've tried about everything I can think of, but no good. Has anyone faced this problem before? Any solutions? Screenshot bellow of the HTTP requests I'm trying to send, but always returns 404 error due to the fact that the id query key value being sent is a string, and not an integer.

Thanks in advance!

Categories:

Using flows

I have the same question (0)

All responses (8)

Answers (1)

v-yueyun-msft on at

Like (1)

Report

Hi , @special-analyst

According to your screenshot , you are using the Http action to send a request. And you need to pass the integer instead of the String.

First , you can try to click here and change the json :

Second, you need to ensure your request can send successfully in Postman to test:
Postman API Platform | Sign Up for Free

If this reply can help you , you can click mark this reply as solution (Accept solution) which can help more people, thanks in advance!

Best Regards,

Yueyun Zhang

Was this reply helpful? Yes No
special-analyst 18 on at

Like (0)

Report

Hi, @v-yueyun-msft
How are you?

I also already changed the view to json before and removed the "", but it's still being converted to string. On Postman works just fine, already tried before, but on Power Automate still the same error 404 because the value persists being sent as string. Prints bellow.

HTTP request
Response on Power Automate

Response on Postman

Was this reply helpful? Yes No
v-yueyun-msft on at

Like (1)

Report

Hi , @special-analyst

Thanks for your quick response! And sorry for my delay response due to having launch.

In this screesshot,

I'm sorry, but I haven't seen this kind of /: http request.In general, a normal URL request passes a parameter using:

?id=123

Or can you try to move the Id Query to the URI property:

Best Regards,

Yueyun Zhang

Was this reply helpful? Yes No
special-analyst 18 on at

Like (0)

Report

Hey, @v-yueyun-msft!
Don't worry, friend! Thank you for your responses. I didn't even thought that someone would answer me so soon.

Yesterday I also thought about this possibility. I didn't built it the way you mentioned, but even this way, no luck for me. Check out Postman response bellow.

Pipedrive is a cloud-based CRM tool.

You can fork Pipedrive's collection through this link. It's the oficial API collection from Pipedrive. I'm trying to delete a person and update a deal.

If you want to get deep, you can create a Pipedrive sandbox account here, go to "Contacts" > "Persons" > "+ Person", create a person, access it, get it's ID through the URL and test deleting it through API.

Was this reply helpful? Yes No
v-yueyun-msft on at

Like (1)

Report

Hi, @special-analyst

Thanks for your response! And thanks for the api you provide to me!

Sorry for that i have not seen the Path variable in my work experience. And i found that it has the another request also can delete the Person.

Can you try to check if this api can meet your need :

Best Regards,

Yueyun Zhang

Was this reply helpful? Yes No
special-analyst 18 on at

Like (1)

Report

Hey, @v-yueyun-msft!

Aparently this does solve the problem related to delete a person, but it doesn't solve the problem related to update a deal, as I mentioned before that I'm also trying to do. There's no workaround for updating a deal. Simmilarly, updating about anything on Pipedrive through Power Automate faces the same problem. I'm pretty sure I should be able to send an integer as a query key value on a HTTP request, and not being able to do so seems to be a bug. I can't mark your reply as a solution, because we must agree in one thing: the actual problem isn't solved.

If our option is to require different API methods to do the same thing, I'm gonna file a bug somewhere, because Postman can make the exact same request successfully without screwing things up.

Anyways, thank you for your fast replies and for your time, friend!
Perhaps someone else can also contribute with our discussion.

Sincerely,
Luis Aguiar

Was this reply helpful? Yes No
Verified answer

v-yueyun-msft on at

Like (1)

Report

Hi , @special-analyst

Today I looked up the interface documentation, and I found that this Path variable is actually the path variable definition in the url.🤣 Sorry for that i have not used the Path variable in Postman...

So for your this api:

You just need to add the integer here in the url:

If this reply can help you , you can click mark this reply as solution (Accept solution) which can help more people, thanks in advance!

Best Regards,

Yueyun Zhang

Was this reply helpful? Yes No
special-analyst 18 on at

Like (0)

Report

Hey, @v-yueyun-msft
How are you?

WOW! That worked perfectly. I'm definetely ashamed of not being able to figure it out. But even funnier, I contacted Microsoft Support and they didn't know how to solve the isue haha

Congrats, my friend, and thank you so much! You definetely saved me, and probably many others.

See you around!
Sincerely
Luis Aguiar

Was this reply helpful? Yes No