Skip to content

Commit

Permalink
Update content/integrations/chat/microsoft-teams/sending-a-message-to…
Browse files Browse the repository at this point in the history
…-channels.mdx

Co-authored-by: Meryl Dakin <[email protected]>
  • Loading branch information
mattmikolay and meryldakin authored Nov 21, 2024
1 parent bcaf2dc commit 1d952e4
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ If you already use Knock's tenant concept to power other 'account-based' feature

[Objects](/concepts/objects) in Knock are flexible abstractions meant to map to a resource in your system. Each individual object in Knock exists within a `collection` and requires an `id` unique to that collection.

In the context of Knock's Microsoft Teams integration, objects serve two purposes. First, they store the Microsoft Teams channel or channels you want to notify. Second, they act as the recipient of the workflow that sends a message to Microsoft Teams.
In the context of Knock's Microsoft Teams integration, objects serve two purposes. First, they store the Microsoft Teams channel or channels you want to notify. Second, they act as the recipient of the workflow used to send a message to Microsoft Teams.

<Callout
emoji="💡"
Expand Down

0 comments on commit 1d952e4

Please sign in to comment.