Teams is a business communication platform where people can work together more effectively, connect all their software tools and services, and find the information they need to do their best work — all within a secure, enterprise-grade environment.
With the Microsoft Teams destination, Hightouch can serve as a notifier for various changes. This is a very flexible integration, but here are a few example use cases:
Notify your customer success teams when product usage for a key account suddenly drops
Notify an account executive when product usage surpasses a certain threshold
Send a daily summary of the number of sign ups, compared to the same day last month
Send a daily summary on the adoption of a core feature
Hightouch will not send any messages on the initial run to prevent a flood of
messages to your channel. Messages will start after the this initial sync.
Hightouch supports sending messages based on rows that have been added, changed, or removed since the last sync run. Each row is sent as an individual message and can be sent to different channels and templated with Liquid.
Message formatting is best when the following conditions are met:
You want to write a query, and have Hightouch detect the added and removed rows
You want a custom message sent per each added and removed rows
Hightouch supports both sending messages to a specific channel that the Hightouch bot is part of, or by pulling the channel ID each row. Enable the "Use column" toggle to dynamically set the target channel.
The batch message mode is similar to the normal message mode, except it sends all rows in the query results rather than only added, changed, and removed rows since the last sync.
This mode also allows you to specify how many rows are sent per message, which can range from 1 to 20. With 1 row per message, it would be similar to the message mode, whereas 20 rows per message would be similar to a tabular representation.
This format is good for the following scenarios.
You want to write a query, and have Hightouch push a message containing all rows, formatted as a message, to Microsoft Teams
You don't want Hightouch to detect added, changed, and removed rows, but instead want to send all rows on each query run
For each message, Hightouch allows setting the subject and row content. Only the row content is required. The row content is repeated per row in the message and has access to the row values via templating.
For both the message and batch message modes, Liquid templating is supported. The most important implication of this is that columns from the added or removed row can be accessed as part of the message body. Here is an example message making use of Liquid to insert a column into the message.
User with name {{ row["name"] }} and email {{ row["email"] }} has signed up
Table formatting sends all of your query results formatted as a text table as messages to Microsoft Teams. This mode is recommended only for small sets of data.
This format is good for the following scenarios.
You want to write a query, and have Hightouch push a message containing all rows, formatted as a table, to Microsoft Teams
You don't want Hightouch to detect added and removed rows, but instead want to send all rows on each query run
If you see a Need admin approval page appear when accessing Microsoft's OAuth login flow, your Azure Active Directory user account might not have the necessary permissions to connect applications to your organization.
Ask one of your Azure organization's admins to edit your user account permissions.
To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . We're here to help.
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.