You’re offline. This is a read only version of the page.
Hello Power Users,
I'm looking for a solution to update Planner Tasks Details via Graph API in an automated work flow.
I'm using non-premium actions.
I'm using this REST doc: https://learn.microsoft.com/en-us/graph/api/plannertaskdetails-update?view=graph-rest-1.0&tabs=http
I'm using the same account in Graph and Power Automate.
I've successfully PATCH via Graph Explorer.
In Power Automate when I use the same URL/URI I get this message:
(I've tried Send an HTTP request [DEPRECATED] and Send an HTTP request V2 to the same results.)
Upon further investigation it seems /planner is not supported in these Send HTTP actions. Is this correct?
Send an HTTP request:
Send an HTTP request V2:
As a new PA user I will say everything has been intuitive until this point.
I just found this post and I'm experiencing the same thing. My flow even looks identical and this user got it working but I get the URI path is not a valid Graph endpoint..message. https://powerusers.microsoft.com/t5/Building-Flows/Update-task-detail-Show-on-card-by-Send-HTTP-request/td-p/2137812
What am I missing here?
Thanks for reading PA community. Any insight is welcome and will be greatly appreciated.
How inconsistent of them. Thanks for the information. Using Built-in HTTP requests is not the route to go if M$ will just pull the cord on working flows. Since it was working for you, 4 months ago, does it fail today even though the v1 is still an option from the PA Choose an operation interface?
Yes, of course. Without this then I wouldn't have been able to get it working in Graph Explorer.
Did you also include the Request Headers?
Authorization : Bearer {token}. Required.
If-Match : Last known ETag value for the plannerTaskDetails to be updated. Required.
Request body
Hi @ridgetech119,
I am that user who got that working, 4 months ago 😁. Since that time Microsoft has deprecated the Send HTTP request v1 action, which I used for the solution. The v2 action is limited to the me and users 1st segment.
You are using the planner segment, which is not allowed in that v2 action.
You can use a HTTP action for this instead, however that is part of a premium connector.
#1
Michael E. Gernaey
497
Super User 2025 Season 1
#2
David_MA
436
Super User 2025 Season 1
#3
Riyaz_riz11
244
Super User 2025 Season 1
Share
Report
All responses (
Answers (