The Workflow Structure

Using the template allows you to identify if you've already alerted on the particular incident. Most systems include something in the JSON body with the webhook payload that will be an incident ID. You can store this in that template and then filter if that incident exists or not in early in the workflow

Workflow Outline

This particular workflow will work for anything that uses Atlassian Status Page for sending out webhooks. I only wanted to alert on incidents and not all page updates, so I first filter on the existence of incident in the JSON:

{{ CTX.body.incident is defined }}

If true, I then load the "lookup_table" in a data alias under the "Incident" transition:

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

Once I've done that, I can then split on if the incident has already been alerted or not:

{{ CTX.body.incident.id not in [item.smtp2go_incident_id for item in CTX.lookup_table] }}

If this evaluates to false, the other transition is "On Success".

Yeah, one note with how this is shown. I was dumb and didn't build one master version that does each different system that uses Atlassian Status Page. They are always the same. That's a goal for the future to go back and merge them all into one workflow with a different trigger and variable configuration for each to simplify if I need to update the process.

If the action needed is a new card, it sends the card, gets the message IDs, and appends that to the script template list. It then updates the template.

If the incident has been alerted previously, the card is updated with new incident information. It ends up looking like this: