Workflows: MS Teams

This article explains the Microsoft Teams node that can be configured as part of Workflows. Learn more about using workflows here. This node can be used to send notifications over Microsoft Teams to other members of the organization.

Configuring the MS Teams Workflow

Click on the block and start editing on the panel that appears on the right side.

‍

Step name

This is the name that appears in the Workflow on the left side. If there are multiple MS Teams nodes in the workflow, set different step names like NotifyHR, NotifyFinance etc.

‍

Authenticate

Click on Authenticate. This will redirect you to the login page for your Microsoft account. You can select your organization's Microsoft account and give the necessary permissions. Once you have authenticated, your teams and channels will be automatically loaded.

‍

Select Team

Select a Team from your Teams account where you want the notifications to be sent.

Select Channel

Select a Channel from your Team where you want the notifications to be sent.

Body

Specify the body of the notification here. You can also use variables from the App to customize the body. Learn more about using variables in workflows here.

‍

Parent Step

Parent step refers to the function which is just above the MS Teams node. Here, it is the Start function.

‍

Enable this Step

This step is enabled by default. You can disable this step to prevent this step and the steps below this one from executing.

Receiving the notifications

Once the Workflow runs, notification will be received on your Teams Account in the selected Channel.

Note on Workflows and Bulk Operations

Workflows in Clappia run on individual submissions, such as when a user submits or manually edits a record. However, when using Bulk Upload or Bulk Edit from the Submissions tab, workflows are not triggered, even though new submissions may be added or existing ones updated.

This is because workflows are designed to process one submission at a time. Triggering them for bulk operations can lead to incomplete or inconsistent results, especially for complex workflows.

If you need workflows to run after a bulk operation, currently you will need to open each submission manually and save it. This will count as an edit and trigger the workflow normally.