Someone suggested me a Slack “connector” - just asking. In fact a webhook in eramba would not be hard to build (that triggers on certain conditions as part of the notification engine)
1 Like
If you’re building Slack, can you build M$ Teams too?
That will be great. We use heavily Slack and we could create a Slack bot/app to warn people that is time for them to do a control.
This is what we call “webhooks” , api calls made by eramba when “something happens”. in eramba “when something happens” is most of the times either:
- status changes on an object
- notifications triggering (notifications have recipients, which ties well into users not channels btw)
This will be part of this functionality: Feature - Custom Defined Role Names and Dynamic Status
[this post is a continuation to the dynamic status post found here]
Notifications will need an update for status - currently we have notifications that trigger against a date (-15,-10, etc) and in certain cases when a status changes (audit completed). Since you will be able to define your own status, it makes sense that you are able to define a new “Warning” notification on every section (and this is important s today warning notifications do not exist on every section) where dynamic status exist.
The user can choose “Dynamic Status Notification” from the first drop down and then on a second drop down they can choose the dynamic status that will be triggered from the list of configured dynamic status.
Warning: users CAN NOT delete dynamic status if they have a configured notification.
On top of this we want to expand all notifications (not just dynamic) to include webhooks not just emails, for this we’ll need to update the current modal for notifications to include Webhooks, we basically need one more tab on the notification engine called that way.
To define a webhook we need the following information:
- Method (POST by default)
- EndPoint URL (must be a valid URL)
- Headers (this is an paragraph field where user defines http headers one line below the other)
- Payload (same as above)
- Timeout (by default 5 seconds) … this is important because if the end-point is unresponsive the cron job will get stuck with this process for sure as many notifications could have been configured.
Note: Payload and Headers can use macros, in the same way notification uses them.
We need a “Test” button , when pressed by the user we open a popup with the http response received by the definition set above.
Is important that when the notifications triggers we store records just as we do with notifications, this is important for debug purposes. today we send emails to a email queue (which in the end stores records so users can tell what happened when), we need to re-use this magic for webhooks.
Under description we need to log the call as it was triggered and the response.
gettin’ there
1 Like
Hello,
having successfully set up some email notifications in Eramba,
I want to send them out in parallel to Slack (you know what it’s like… some colleagues have very busy inboxes and pay more attention to Slack… other colleagues work the other way round 
I guess most of the info I will need to going to be on Sending messages using Incoming Webhooks | Slack ?
(And I need to ask for a webhook address from my Slack system administrator).
But I just wondered if anyone on the Eramba community has any examples of Slack notifications they successfully created - the JSON headers and content are a bit outside my comfort zone…
HEADERS:
Content-type: application/json
BODY:
{"text":"Test Webhook"}
1 Like
Thank you 
I am hoping to get this working this week, with a little help from my IT team… will likely post back with an update about how I got on