Statuspage + Memtro

Ask what is down on your status page and what customers were told during an outage.

Connect Statuspage with an API key and Memtro reads the status pages your user can see, incidents and scheduled maintenance with status, impact, affected components and every update posted, each incident's postmortem, and each component's current status. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can open and update incidents, schedule maintenance, set component status, and write or publish a postmortem, all public at once, and permanently delete incidents or components. Subscribers are emailed or texted only when you ask.

In Memtro

What you can do with Statuspage in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Statuspage tool, reads what it needs, and answers with the source cited.

What it does

  1. 01The status pages your Statuspage user can see, with their ids and public addresses
  2. 02Incidents newest first with name, status, impact, affected components, latest update and link, and scheduled or active maintenance
  3. 03One incident in full: every update posted, affected components, timings and the postmortem
  4. 04Each component's current status, or only the components not operational now
  5. 05When asked and granted, opens an incident, posts updates or resolves it, corrects a posted update, schedules maintenance, and sets, adds or renames components, all public at once and notifying subscribers only when asked
  6. 06When asked and granted, writes or publishes a postmortem, saves an incident template, and permanently deletes an incident or a component with its uptime history

Acts when asked

When you ask it to

These tools change something in Statuspage. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.

  1. 01Open an incident on a status page, optionally notifying subscribers
  2. 02Update an incident: post an update, change its status (resolve it), impact or affected components
  3. 03Schedule a maintenance window
  4. 04Delete an incident from the page, permanently
  5. 05Correct the text or time of an update already posted
  6. 06Set a component's status, or rename or redescribe it
  7. 07Add a component to a page
  8. 08Delete a component, permanently
  9. 09Write an incident's draft postmortem, or publish it to the page
  10. 10Save an incident template

Events

When it happens

Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Statuspage for you. Each event can start a job, with the event as its input. Statuspage signs nothing, so the long random address is the only check: treat it as a password.

Events and webhooks
  • 01A component's status changed
  • 02An incident was created or updated
In practice

Ask it like you would a colleague

Once Statuspage is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.

Statuspage + Memtro
  • Is anything down on our status page right now?

  • What did we tell customers during last Tuesday's outage?

  • Is any maintenance scheduled for this week?

  • Open an incident for degraded API performance and notify subscribers

  • Resolve the login incident with an update that the fix is deployed

01

After an outage

The founder is writing to BigCo about last week's outage. She asks Memtro what customers were told. It reads the incident in full and gives every update posted, the affected components, the timings and the postmortem.

02

Posting an incident

During a slowdown, on-call engineer Marco Rossi asks Memtro to open an incident on the API component and tell subscribers. Memtro shows the wording, then opens the incident with the API marked as degraded performance. It appears on the public page at once and subscribers are emailed and texted.

Teams

Where it fits

The teams that lean on Statuspage most, a question each of them asks, and what they connect beside it.

Better together

Works with

A record in Statuspage is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.

Also in Engineering and operations

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

Setup

How to connect

Connect withAPI key
  1. 1

    At manage.statuspage.io open avatar → API info and copy an API key or create one. It is personal, so Memtro sees and changes the pages your user can

  2. 2

    If you have several pages, copy the default page id from the same screen

  3. 3

    In Memtro open Connections → Statuspage, paste the API key, and the Default page id if you have one, and connect

  4. 4

    Ask whether anything is down right now

Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Statuspage tools are the same everywhere.

FAQ

Questions

Can Memtro change anything in Statuspage?+

Only when you ask, and only what it has been granted: open an incident on a status page, optionally notifying subscribers; update an incident: post an update, change its status (resolve it), impact or affected components; schedule a maintenance window; delete an incident from the page, permanently; correct the text or time of an update already posted; set a component's status, or rename or redescribe it; add a component to a page; delete a component, permanently; write an incident's draft postmortem, or publish it to the page; save an incident template. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

Who can use a Statuspage connection?+

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Does Memtro store my Statuspage data?+

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

How do I connect Statuspage?+

API key. At manage.statuspage.io open avatar → API info and copy an API key or create one. It is personal, so Memtro sees and changes the pages your user can.

Can Statuspage start a job?+

Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Statuspage for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.

Connect Statuspage in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time