Send a Microsoft Graph HTTP request action to add members to a group chat

(2) Share

Report

Posted on by CU24041027-0

Hi ,

I am using 'Send a Microsoft Graph HTTP request MS teams action to add members to a MS teams group chat with URI

https://graph.microsoft.com/v1.0/chats/{CHAT-ID}/members

But it gives me below error, I have verified group chat ID and its correct and I am part and owner of this group chat

URI path is not a valid Graph endpoint, path is neither absolute nor relative or resource/object is not supported for this connector. Resources: teams,me,users Objects: channels,chats,installedApps,messages,pinnedMessages. Uri: https://graph.microsoft.com/v1.0/chats/{chat-id}/members

Any idea how to resolve.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

David_MA 14,496 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Based on your API call, you are using this request: Graph Explorer | Try Microsoft Graph APIs - Microsoft Graph. This gets the existing members of a chat and is not for adding a member. Currently there is no Graph API call to add members to a chat.

Instead, you need to use the create a group chat API call, which you can learn about here: Create chat - Microsoft Graph v1.0 | Microsoft Learn. However, if you're doing this in Power Automate, it may be easier to do with these actions Send a message in Teams using Power Automate - Power Automate | Microsoft Learn.

Was this reply helpful? Yes No
CU24041027-0 6 on at

Like (0)

Report
Copy link

Link copied!

Hello David,

I referred to this link for adding members to a chat. It uses the similar api : https://learn.microsoft.com/en-us/graph/api/chat-post-members?view=graph-rest-1.0&tabs=http

Was this reply helpful? Yes No
eliotcole 4,390 Moderator on at

Like (0)

Report
Copy link

Link copied!

You're so right, @CU24041027-0 ... this should work!

I have a feeling that it is broken, and ... there is no public way that we can either tell Microsoft this, or check to see if there is an issue with the connector.

I will assume that you're using the 'Teams' connector, and its 'aaaa' action within, which should allow to reach said endpoints on the Graph API.

I have previously had *some* luck using '/me/chats' ... but that really isn't the point. This should work, and use the user's permissions about what they can and cannot do on the '/chats' endpoint, automatically, via related Entra ID permissions.

I am seeing a whole host of errors, whether I include odata metadata or not, around not valid endpoints, or invalid bind properties ... it's crazy frustrating and all because they decided that we could no longer use the Groups connector as a defacto 'Graph' connector a few years back. V. Frustrating!

Was this reply helpful? Yes No