Microsoft Teams currently provides 4 triggers that can start a workflow and 14 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
New Channel Message
Triggers when a new message is posted in a channel.
New Channel
Triggers when a new channel is created in a team.
New Chat
Triggers when a new chat is created.
New Chat Message
Triggers when a new message is received in a chat.
Create Channel
Create a new channel in Microsoft Teams.
Send Channel Message
Sends a message to a teams's channel.
Send Chat Message
Sends a message in an existing chat.
Reply to Channel Message
Post a reply to an existing channel message.
Create Chat & Send Message
Start a new chat and send an initial message.
Create Private Channel
Create a new private channel in a team.
Get Chat Message
Fetch a specific chat message by chat and message ID.
Delete Chat Message
Soft-Deletes a message in chat.You can only delete messages you sent.
Get Channel Message
Fetch a specific channel message by team, channel, and message ID (optionally a reply).
Find Channel
Finds channels by name.
Find Team Member
Finds a team member by email or display name.
Request Approval in Channel
Send approval message to a channel and then wait until the message is approved or disapproved
Request Approval from a User
Send approval message to a user and then wait until the message is approved or disapproved
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Microsoft Teams event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Channel Message
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Microsoft Teams action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Channel
Combine Microsoft Teams with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
New Channel Message
Finishes with
Create Channel, then preserve the outcome in Coherence
The exact authentication fields depend on Microsoft Teams. The workflow structure stays straightforward:
Authorize the Microsoft Teams account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Microsoft Teams or provide a complementary trigger or action.
Microsoft Teams currently provides 4 triggers that can start a workflow and 14 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Microsoft Teams currently lists 4 triggers and 14 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Microsoft Teams triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
