•The Create Object action creates a single Microsoft Teams object using the POST HTTP method.
The following snippet is a sample request payload example to create a channel within a specified team.
<root> <displayName>Sample channel 1</displayName> <description>This channel is a sample channel</description> <membershipType>standard</membershipType> </root>
The following snippet is a sample response payload example of the created ticket:
<root> <membershipType>standard</membershipType> <odata.context>https://graph.microsoft.com/v1.0/$metadata#teams('ad2e7f8c-8bd4-44f1-a15c-d9a782025066')/channels/$entity</odata.context> <displayName>Sample channel 1</displayName> <isArchived>false</isArchived> <webUrl>https://teams.microsoft.com/l/channel/19%3abf15b4d4eaf84f8eb00a488f674be763%40thread.tacv2/Sample+channel+1?groupId=<Group_ID>&tenantId=<Tenant_ID></webUrl> <createdDateTime>2025-04-08T22:59:50.6160702Z</createdDateTime> <description>This channel is a sample channel</description> <id>19:bf15b4d4eaf84f8eb00a488f674be763@thread.tacv2</id> <isFavoriteByDefault>false</isFavoriteByDefault> <email/> </root>
•The Delete Object action deletes a single Microsoft Teams object using the DELETE HTTP method.
To delete an entity, you must specify values in the entityType and entityId fields. For example, to delete a team by ID, you must specify the entity type as teams and the entity ID of the team.
After the team is deleted, if you try to call this action a second time, you will receive the following error:
<root> <error> <code>NotFound</code> <innerError> <date>2025-04-08T23:20:24</date> <code>1</code> <client-request-id>71b1165a-66f1-4a49-b1d8-a938b5098740</client-request-id> <message>SoftDeleted-Thread was not found as it is soft-deleted.</message> <request-id>71b1165a-66f1-4a49-b1d8-a938b5098740</request-id> </innerError> <message>NotFound</message> </error> </root>
•The Update Object action updates and deletes using soft delete a single Microsoft Teams object.
The following snippet is a sample payload example to update a group of properties:
The jsonContent will be replaced by attachmentContent, which is a separate input property. The attachmentContent property is in JSON format and must be properly formatted.
The following snippet is a usage example:
{ \\"title\\": \\"This is an example of posting a card\\", \\"subtitle\\": \\"<h3>This is the subtitle</h3>\\" }
The following snippet is a sample response payload:
<root> <summary/> <lastModifiedDateTime>2025-04-08T23:34:31.631Z</lastModifiedDateTime> <lastEditedDateTime/> <attachments> <teamsAppId/> <contentUrl/> <name/> <id>74d20c7f34aa4a7fb74e2b30004247c5</id> <contentType>application/vnd.microsoft.card.thumbnail</contentType> <content>{
 "title": "This is an example of posting a card",
 "subtitle": "<h3>This is the subtitle</h3>"
 }</content> <thumbnailUrl/> </attachments> <odata.context>https://graph.microsoft.com/v1.0/$metadata#teams('9f3781dd-1838-4e5d-9717-21ebf4419d0d')/channels('19%3AuHcmVFwkdTf_vdtcymNtE8AbM4I1ZEgnbmBUt_Kvrys1%40thread.tacv2')/messages/$entity</odata.context> <chatId/> <replyToId/> <subject/> <importance>normal</importance> <createdDateTime>2025-04-08T23:34:31.631Z</createdDateTime> <deletedDateTime/> <policyViolation/> <locale>en-us</locale> <body> <contentType>html</contentType> <content><attachment id="74d20c7f34aa4a7fb74e2b30004247c5"></attachment>Content 4.</content> </body> <channelIdentity> <teamId>9f3781dd-1838-4e5d-9717-21ebf4419d0d</teamId> <channelId>19:uHcmVFwkdTf_vdtcymNtE8AbM4I1ZEgnbmBUt_Kvrys1@thread.tacv2</channelId> </channelIdentity> <messageType>message</messageType> <webUrl>https://teams.microsoft.com/l/message/19%3AuHcmVFwkdTf_vdtcymNtE8AbM4I1ZEgnbmBUt_Kvrys1%40thread.tacv2/1744155271631?groupId=<Group_ID>&tenantId=<Tenant_ID>&createdTime=1744155271631&parentMessageId=<Parent_Message_ID></webUrl> <mentions/> <etag>1744155271631</etag> <from> <application/> <device/> <user> <odata.type>#microsoft.graph.teamworkUserIdentity</odata.type> <displayName>ABC</displayName> <tenantId>29ecc36f-ba8d-4f7c-b037-22269e437749</tenantId> <id>c348b735-5c8b-48a4-be80-064e98b5ff9a</id> <userIdentityType>aadUser</userIdentityType> </user> </from> <reactions/> <id>1744155271631</id> <eventDetail/> </root>
Additional action parameters
queryParams is the object that holds query key-value pairs.
The following example is used to display the top 10 records of a particular entity type:
ConsistencyLevel - When specified, the eventual value enhances the query capabilities of actions using the GET method.
Prefer - To include unknown member types, you must provide the include-unknown-enum-members value. Additionally, the Prefer header determines merge behavior. For example, if you attempt to PATCH a nonexistent object and set the Prefer header value to create-if-missing, the object will be created.