title: "Script Hooks: Integrating Retrospect with Slack" created_at: 2017.01.27 updated_at: 2020.03.11 category: Hooks ---
Slack is an online instant messaging and collaboration tool used by over one million users. One of its compelling innovations is the ability to integrate a wide variety of applications to all go to Slack. With Script Hooks, you can monitor Retrospect from Slack as well.
Download the example Retrospect script hooks from our website.
For Mac, copy the file "RetroEventHandler.sh" from the Slack folder to
For Windows, copy the file "RetroEventHandler.vbs" from the Slack folder to
In either case, edit the file in your favorite text editor. Find the text:
You will need to set up a Slack web integration to get a URL to replace the placeholder above with.
This document assumes you already have a Slack account. If you do not, you can set one up for free at https://slack.com/.
Once you do, you will need to create a new incoming WebHook.
This will create a URL that Retrospect (or more correctly, the Slack retroEventHandler) can send its messages to. The only requirement here is to pick which Slack channel you wish Retrospect’s notifications to go to.
Once you choose Add Incoming WebHooks integration, you will get a screen like the one below with a WebHook URL.
Copy this URL into the Slack Retrospect eventhandler in place of the
Save the file. You are now done. You do not need to restart the Retrospect engine or application for it to start using the script.
To test, run a short backup. This should result in a set of messages similar to the following:
If you do not get any messages, confirm the URL did not get cut off or have extra characters added. You can also test just the script by opening up a terminal or cmd window, and cd’ing to the eventhandler folder. Then type:
retroEventHandler "StartApp" "2/10/2017 12:01 AM" "true"
If there are any errors, they should display in the terminal or cmd window and point you toward a solution.
Slack now requires TLS 1.2 to be enabled, and older operating systems, including Windows 7 and Windows 2008r2, do not have TLS 1.2 enabled by default. This causes Retrospect script hooks to fail until TLS 1.2 is enabled.
Last Update: 11 de marzo de 2020