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
  • In Rewst, create a new workflow
  • For now, just create a single noop action
  • Add a webhook trigger
  • Copy the webhook or leave tab open for reference
  1. Automations
  2. Automated GitHub/GitBook Update Notifications

1. Set up a Basic Workflow

Before getting to work on the GitHub side, one of the bits you'll need from your automation platform is a webhook to enter into the notification settings.

1

In Rewst, create a new workflow

Remember to follow best practices when naming your workflow. Just as Rewst has undergone a lot of standardization of naming, your organization should be doing the same.

2

For now, just create a single noop action

Did you pronounce this noop or noop? Debate about it in the ROC Open Mic chat.

Don't forget to hit publish to save otherwise you'll see a failure in your workflow history once the webhook notifications are set up in GitHub

3

Add a webhook trigger

This trigger only needs to live at the parent organization level, so there is no need to toggle on the managed organizations or select any from the dropdown.

4

Copy the webhook or leave tab open for reference

PreviousPrerequisitesNext2. Fork the GitHub Repository

Last updated 4 months ago