Get the overall Google Workspace statusAnswer 'is Google Workspace working' in one step, as one sentence a workflow can post straight to chat. It comes back with a plain yes or no, the worst status across every service, and the names of any services currently affected. Use it for a morning status post, or to hold a workflow back while Google is having a bad day.
Check whether a service is upCheck one service, such as Gmail or Google Drive, and get a flat answer the next step can read without digging into a list: is it available, what is wrong if it is not, when that started and what Google last said about it. Google publishes no such field, so it is worked out here from the incidents that are still open. Use it to gate a step on whether a service is working, or to tell a helpdesk it is Google rather than them.
List incidents happening nowList only what is going wrong right now, worst first, with the services each incident affects and the latest thing Google said about it. This is the one an alerting workflow runs on a schedule: narrow it to the services your team depends on, and to outages only if a notice is not worth waking anyone for. It says so plainly when there is nothing to report.
List services and their statusList every Google Workspace service the dashboard covers, each with its status right now, how many open incidents name it and when it last had one. Narrow it to the statuses you care about to get just the services in trouble. It is also the one step way to see what this integration can be asked about, and to check the connection works.
List new and updated incidentsList everything Google has posted since a moment you give it, so a workflow running every few minutes can alert on what is new instead of re-reporting the same incident. Each one says whether the incident itself is new or was already running, and carries only the updates posted since. This is not the same question as searching past incidents: that asks when an incident was happening, this asks when Google last wrote about it.
Search past incidentsSearch the incidents Google is still publishing, narrowed however the question needs: by service, by dates, by how bad it was, by whether it is resolved, or by words in what Google wrote. An incident counts as in the dates if it was running at any point in them. The dashboard keeps only roughly the last year, so a search reaching further back is trimmed to what exists and the result says it was, rather than coming back quietly short.
Get an incident with its updatesGet one incident in full, including every update Google posted as it went, oldest first. Use it after a search or an alert to write up what happened, or to see how the story changed. The dashboard keeps only roughly the last year, so an incident older than that is reported as gone rather than as never having happened.
Get a service's recent incident historyHow one service has actually been doing, counted rather than listed: how many incidents, how many were real outages, how long they added up to, which was the longest and how long it has been since the last one. The last ninety days unless you give it dates. Use it for a monthly reliability note, or to answer whether the problem someone is complaining about is a pattern.
