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
  1. Automations
  2. Teams Notifications Azure Bot

Working with the Responses

PreviousAssign Resource to TicketNextSystem Incident/Maintance Notifications

Last updated 11 months ago

Your response handler workflow will get pinged on any "action" the bot can see. Bot installed as an application in a Team, newly created channels for a Team it's already installed in, channel deletion, reactions to posts made, comments made on posts, etc. What I primarily was working to build out was a workflow that will handle the responses to the different action buttons.

To do that, you need to understand the JSON payload that comes with the bot response. The primary part that you're concerned with is the "body":

There's quite a bit of useful, acitonable information that you can get from the "body"

If you've properly built out your "Action.Submit" "data" fields, then the piece of the "body" that you'll be most interested is "value". Here you'll see the properly formatted approval body needed to send the SME approved service ticket to Azure DevOps

By building this information into the JSON for the action, you'll be able to pass the information from the response handler workflow to the sub-workflow and action as needed.

Unexpanded JSON sent to Rewst
"body" JSON Expanded
"value" JSON Expanded