Statuspage Strawberry

Hand the Statuspage incidents to a companion

One sentence in, and a companion has been through the Statuspage incidents, put them where you can read them, and marked the ones it was not sure about.

Open the incident. Check it against something else. Write the change. Move to the next one. That is the Statuspage afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a incident until you approve it.

What it can do is exactly what Statuspage exposes to an account you authorise and nothing beyond it: 4 operations, 1 read and 3 writes. In practice that means it can create a maintenance, update an incident and create an incident, and work across the incidents, active incidents and maintenances.

The Statuspage API stops at Statuspage. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.

What does it already know about your active incidents?

1 of the 4 operations is a read.

Your account, not a guess at it: a companion can fetch active incidents, and the full list below is the whole list, with nothing inferred from Statuspage's documentation.

The incidents are what most of this inventory is about, alongside the active incidents. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of Statuspage admin becomes a queue you review.

  • Fetch Active Incidents

Can it change a incident without asking?

All 3 write operations wait for you.

A companion can create a maintenance, update an incident and create an incident, and each one is staged on an approval card first: you see the incident, the field and the new value before it lands in Statuspage.

Nothing in Statuspage is sent, changed or deleted on your behalf without that click, and a rejected card leaves the incident exactly as it was. The gate is the same one on every surface, described at security.

  • Create Maintenance
  • Update Incident
  • Create Incident

Can it fetch active incidents every morning by itself?

Yes.

Saved as a routine, the Statuspage incidents pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.

The product and engineering playbook catalogues the other recurring shapes of the infrastructure checks, the Statuspage incidents sweep among them, and finished runs are published at real runs.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. Connect your Statuspage account and a companion works 4 operations in it, with every change staged for your approval. You authorise the connection yourself and the credential is held encrypted where Strawberry never receives it.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide