Brian's Integration and Automation Notes
  • Welcome!
  • Allow Me to Brag a Bit
  • About
  • Integrations
    • ConnectWise Home
      • Authentication
      • API Documentation
  • Automations
    • Teams Notifications Azure Bot
      • Acknowledgement
      • Considerations
      • The Basics/Getting Started
        • Create a Response Handler Workflow in Rewst
        • Getting the IDs from Teams
      • Two Stage Message Process
        • Formatting the Initial Message
        • Getting the Message IDs
        • Formatting the Message Update
      • Formatting Action Buttons
        • Approve/Deny
        • Assign Resource to Ticket
      • Working with the Responses
      • System Incident/Maintance Notifications
        • Admitting Defeat on the Database
        • The Workflow Structure
      • Resources
    • Automated GitHub/GitBook Update Notifications
      • Prerequisites
      • 1. Set up a Basic Workflow
      • 2. Fork the GitHub Repository
      • 3. Set up Automatic Updates
      • 4. Set up notifications in GitHub
      • 5. Set up Remaining Workflow Actions
  • ConnectWise PSA Actions
    • About
    • Assigning Resources to Tickets
    • Ticket Assignment Note
    • Unbundle Ticket
    • Sales Activity Assignment Note
Powered by GitBook
On this page
  • IDs Needed
  • From the Bot Response Webhook Handler
  • Using Graph API
  1. Automations
  2. Teams Notifications Azure Bot
  3. The Basics/Getting Started

Getting the IDs from Teams

PreviousCreate a Response Handler Workflow in RewstNextTwo Stage Message Process

Last updated 11 months ago

IDs Needed

When you work with proactive notifications, you need three IDs to be able to send a notification to Teams

From the Bot Response Webhook Handler

There are several ways to go about getting these IDs but one helpful way is that every time your bot is added to a new Team, those IDs get sent to the Rewst webhook. New channels that also get added to a team after the bot is installed are also sent. You can build a sub-workflow that handles how to document those IDs based on the response you get in the JSON payload.

Using Graph API

A second way to get these IDs is to use the Graph API:

With those two calls you can discover the IDs for the team and channel. Using this way, you shouldn't need to dig for tenant IDs since to make the calls you would have to have had those in your system already.

LogoList teams - Microsoft Graph v1.0MicrosoftLearn
Graph API Call to List Teams to Obtain IDs
LogoList channels - Microsoft Graph v1.0MicrosoftLearn
Graph API Call to List Channels of Teams to Obtain Channel IDs