Connect an incoming webhook once and any notify step can post to that Google Chat space. For teams on Google Workspace, it keeps monitoring alerts alongside everything else the team is already discussing.
If your organisation runs on Workspace, this is the chat destination that needs no new account anywhere.
Everyone in the space sees the alert, which is what you want for shared awareness of a service being down.
Separate connections let each service route to the space of the team that owns it.
Use the space for awareness and an email or phone call for the person who actually has to act.
The connection decides where an alert goes. These settings decide how often it goes there.
The default. The step fires once and resets on recovery, so a long outage does not turn into a wall of messages.
Switch the step to fire on every matching check when you want a continuous signal instead of a single alert.
Fifteen minutes by default, so a monitor bouncing down and up will not re-send inside that window.
Write the message with placeholders such as flow, state, detail and duration so the alert carries context.
Put the step behind set hours and days if it is informational, and leave the critical path ungated.
Add a Repeat alert block before the step to keep sending on an interval while the monitor stays down.
Add the connection, send a test, and draw a line to it from your first monitor.