Contents:

• Overview
• Authorizing Microsoft Teams
• Unauthorized Endpoint Error
• Node Usage and Customization
• Summary

 

Overview

The Microsoft Teams Send Notification Node gives you the ability to send Notifications to your Microsoft Teams inside your FlowBuilder Graphs. Using the Microsoft Teams Send Notification Node allows you to send a notification to MS Teams from anywhere in your Graph the Node is located.

Example: Rachel is the LeanData administrator for Lighthouse Development. She uses the Microsoft Teams Send Notification at various points in the Lead Router graph to be able to notify a rep, through MS Teams, of a hot Lead as it is being routed.

 

Authorizing Microsoft Teams

Before you can use the Microsoft Teams Send Notification Node, you must authorize the integration.

• Ensure the appropriate remote site setting is configured in Salesforce to use LeanData Integrations. For more information, see LeanData Admin - Adding the LeanData Remote Site Setting.
• From the LeanData App, navigate to Integrations > Routing tab and click the Get Started button on the Microsoft Teams tile.

• Specify the correct User Field to help LeanData map Salesforce User Emails to Microsoft Teams User Emails to direct notifications to the right recipients. LeanData will identify Microsoft Teams Users with the corresponding Salesforce Users by matching email addresses across orgs, by referencing the User field you select here.

• Click the Authorize Microsoft Teams button.

Two Methods to Authorize Microsoft Teams

There are two methods of authorizing Microsoft Teams with LeanData, depending on whether you want a Global Admin, Cloud Admin, or Application Admin to be the user that sends messages in Teams from LeanData or you wish to designate a different service account user for this purpose.

• Single-step method via granting User Consent: entered user will be Teams messenger for LeanData.
  • Enter the credentials of a user with Global Admin, Cloud Admin, or Application Admin role assignment in Entra.
  • Click Accept.
  • This will be the user that sends messages in Teams from LeanData
• Two-step method via granting Admin Consent: allows service account user to be designated as Teams messenger for LeanData.
  • Enter the credentials of a user with Global Admin or Privileged Role Admin role assignment in Entra.
  • When prompted, select checkbox to “Consent on behalf of your organization”
    • Admin Consent can also be given in Entra by navigating to Entra ID > Manage > Enterprise Application > LD-V2-Teams > Security > Permissions > Grant admin consent, after the integration is added.
  • Click Accept.
  • You may now re-authorize Microsoft Teams in LeanData for a designated service account.
    • To restrict access to this integration to only the designated user(s), you can configure access assignments in the Microsoft Entra admin center.

 

Unauthorized Endpoint Error

In some cases, you may get an unauthorized endpoint error when saving a Microsoft Teams Notification node in your graph. This is typically because a permissions issue with the  the authorizing User is prevents the creation of a required Remote Site Setting.

If you are encountering this error, you may need to manually add a Remove Site Setting in Salesforce. To do so, have a Salesforce Admin follow these steps:

• Navigate to Salesforce Setup > Remote Site Settings.
• Click New Remote Site.
• In the Remote Site Name field, enter MICROSOFT_TEAMS_RSS
• In the Remote Site URL field, paste the following URL: https://graph.microsoft.com
• After entering the Remote Site Name and Remote Site URL, click Save.

 

Node Usage and Customization

You have a number of options to configure the node.

• Node Name
• Description
• Recipients
• Message

Node Name

By default, the Node Name is set to Send Notification. You can change this label to anything you need. We strongly recommend giving this node a meaningful name as you may have multiple nodes with the default name of Send Notification. An example of a meaningful name is New Lead Notification.

Description
This field is not required but we recommend adding a description to document any customizations made to the node. If someone else needs to take over the management of the flow, the description will help them to understand the goal of the customizations.

Recipients

Use the Recipients section to select the recipient of the Teams Notification. To add recipients, click on the Add Recipients button.

Once you click Add RecipientsYou can select multiple recipients. Recipient options include:

• New Owner - This option will send the notification to the new record owner.
• Previous Owner - This option will send the notification to the previous owner of the record.
• Additional Recipients - This option can be used to add additional recipients from the routed Lead record to the notification.
• Teams User(s) - This option will send the Teams notification to the selected Users. User(s).
• Team Channel(s) - This option will send the Teams notification to the selected Team(s) Channels.

After you select the desired recipients, and select Done, your selected recipients will be displayed in the recipients section.

Message

The Message settings gives you the tools to send a MS Teams notification to a user or a record in Salesforce. Use the Message section to compose the MS Teams Notification.

Mention User and Channels Picklist

Use the Mention Users and Channels picklist to insert mentions of the Users and Channels. This picklist has the following options:

• Owner
• Team Channel
• Teams User
• User in Field

Insert a Field Picklist

You can insert fields from the routed record. In addition to these fields, you can also insert a link to the audit log for this specific routing action, or to the audit log for every action performed on this record in LeanData. When selecting your field to insert, select either Audit Log Link or Full Audit Log Link to include the Audit Log URL in your message.

Advanced Settings

The Advanced Settings section gives you the ability to send the record to the next node of the flow as needed.

• Next Node: This option allows the record to be directed to another node in the Router Flow. This can include things like Converting the Lead into a Contact, Creating an Account, etc. You can also set this node to End of Flow. This will stop all LeanData actions at this node instead of sending it to another node.
• Configuration Error: This option provides a fallback edge to keep the record moving through the router flow even if there is a configuration error with the MS Teams integration. A best practice is to route the record to a Send Notification Node to alert the LD Admin that there is a configuration issue.

 

Summary

The Microsoft Teams Send Notification Node is a powerful tool for alerting your reps through Microsoft Teams Notifications of Leads being routed. Use the MS Teams Send Notification Node anywhere in your Lead Router Graphs to send out notifications as needed.

For questions or additional assistance please contact LeanData Support.