nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Connecting Grantmaking with Power Automate

Rijusiddha Drewett

Hi. Is it possible to connect Grantmaking to Power automate via the SKY Add-in SendHttpREquest?

I have used this to build a flow with Raiser Edge Query API but have tried with using the Grantmaking API and just get a 404 no resource found error when I try to make a call. I have mimicked the call on the SKY Developer endpoint test so the actual resource is there and can be calle d by the API.

If not what is the correct way to connect Grantmaking to Power Automate?

Find more posts tagged with

Comments

Glen Hutson

@Rijusiddha Drewett:
Hi. Is it possible to connect Grantmaking to Power automate via the SKY Add-in SendHttpREquest?
I have used this to build a flow with Raiser Edge Query API but have tried with using the Grantmaking API and just get a 404 no resource found error when I try to make a call. I have mimicked the call on the SKY Developer endpoint test so the actual resource is there and can be calle d by the API.
If not what is the correct way to connect Grantmaking to Power Automate?

BBGM API is available via the SendHTTPRequest . What specific endpoint(s) are you having issues with?

Rijusiddha Drewett

@Glen Hutson the one I am testing is Get Requests endpoint. I have tested on the sky api tester, postman and on my own web app and can connect fine. However in power automate I get a 404 response. The request ID is valid.

f5da5c74bccc2845d9c61423c6ac3414-huge-im

7e0ac9dadd01873ef1b7b5b3472d9ffb-huge-im

Glen Hutson

@Rijusiddha Drewett:
@Glen Hutson the one I am testing is Get Requests endpoint. I have tested on the sky api tester, postman and on my own web app and can connect fine. However in power automate I get a 404 response. The request ID is valid.

I did a quick double check and was able to call the endpoint via the Send an HTTP Request Action. In looking at your screenshot, I note two items: 1) You need to have an initial “/” at the beginning of the Relative Path parameter and 2) The Request ID is part of the Relative Path and not a Separate Query Parameter.

8333747b3f87cae2bc62bf8eb762b2a2-huge-im

9799a28a5398285c4d72d6a65034c5ee-huge-im

Rijusiddha Drewett

@Glen Hutson Thank you. It was the parameter bit that was what I needed. I had played around with the leading / already. New it had to be something reasonably simple. Thanks again for the second pair of eyes !