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
  3. System Incident/Maintance Notifications

Admitting Defeat on the Database

Yeah, ok. This is where I had to admit that I was going to need some kind of "database". I still cheated though. Since most systems shouldn't have incidents/maintenance that often - right? - I decided to use a script template in Rewst. The script template is set up in YAML and then immediately converted to JSON using the 

|from_yaml_string

filter. If you've never done this before, you can set a data alias under a noop transition at the start of your workflow and use this as the format:

{{ template("template GUID copied from end of URL for template")|from_yaml_string }}

PreviousSystem Incident/Maintance NotificationsNextThe Workflow Structure

Last updated 1 year ago