Who to call
Tom Reilly, engineering manager at Northwind, asked who was on call for payments. Memtro read the on-call schedules and gave the name on shift with its start and end, alongside the open incidents on the payments service.
Spike.sh + Memtro
Who is on call for payments right now, and what is open?
Spike.sh tells you who is on call and what is burning. You see open incidents, or every incident in a date range, with priority, severity, service and escalation, one incident's activity log and notes, who is on call now, services, integrations, users and status pages. When asked and granted, Memtro can create and page incidents, add or pin notes, acknowledge, resolve or escalate, set priority or severity, add or remove responders, add on-call overrides and post status page incidents and updates. Worth knowing: the key works across the whole organisation with no scopes, and note authors are not named.
In Memtro
What you can do with Spike.sh in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Spike.sh tool, reads what it needs, and answers with the source cited.
What it does
- 01See open incidents, or every incident in a date range, with priority, severity, service and escalation policy.
- 02Read one incident's activity log and responder notes, with the pinned note marked.
- 03Check who is on call now in each schedule, with the shift's start and end.
- 04List services affected by open incidents, integrations, users by name and status pages with their components.
- 05When asked and granted, create or escalate an incident, which pages people straight away, or acknowledge, resolve or add a responder.
- 06When asked and granted, post a public status page incident or update, which emails subscribers only if you ask.
Acts when asked
When you ask it to
These tools change something in Spike.sh. 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.
- 01Create an incident, paging the integration's escalation policy
- 02Add a note to an incident
- 03Pin a note as the incident's current state
- 04Acknowledge incidents
- 05Unacknowledge incidents
- 06Resolve incidents
- 07Escalate incidents to the next level, paging it
- 08Set the priority of incidents
- 09Set the severity of incidents
- 10Add a responder to incidents, paging them
- 11Remove a responder from incidents
- 12Add an on-call override, putting someone on call for a period
- 13Post an incident on a public status page
- 14Post a status update on a status page incident
In practice
Ask it like you would a colleague
Once Spike.sh 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.
Spike.sh + MemtroWho is on call for payments right now?
Which incidents are open and still unacknowledged?
What happened on incident eng-116?
Which sev1 incidents did we have last month?
Acknowledge incident eng-116.
Public status update
Sarah Chen, head of support at Acme Ltd, asked Memtro to post that the login issue was identified. Memtro added an identified update to the status page incident, visible to anyone who opens the page. Subscribers were not emailed, since she had not asked for that.
Teams
Where it fits
The teams that lean on Spike.sh most, a question each of them asks, and what they connect beside it.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- Agent buildersMemory and tools for the agents you buildSolo builder, Platform team, Automation engineer, Whoever signs it off“Search memtro for what we know about Acme before drafting the proposal”Used alongside GitHub, Linear and Slack.
Better together
Works with
A record in Spike.sh 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.
- Work managementSpike.sh with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementSpike.sh with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementSpike.sh with LinearIssues, projects and teams, synced hourly into memory.
- SupportSpike.sh with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportSpike.sh with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportSpike.sh with IntercomCustomer conversations and the people behind them, in your company memory.
- Documents and wikisSpike.sh with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisSpike.sh with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisSpike.sh with ConfluenceSearch and read wiki pages, and write them when you ask.
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.
- GitHub
- AWS CloudWatch
- Sentry
- ServiceNow
- Okta
- Twilio
- AWS CloudTrail
- GitLab
- Bitbucket
- Vercel
- PagerDuty
- Datadog
- Grafana
- incident.io
- Azure DevOps
- CircleCI
- Cloudflare
- LaunchDarkly
- New Relic
- Rollbar
- Snyk
- Better Stack
- Buildkite
- DigitalOcean
- Heroku
- Netlify
- SonarQube Cloud
- Statuspage
UptimeRobot- Axiom
- BugSnag
- Checkly
- Hetzner Cloud
Honeycomb- Pingdom
- Render
- Statsig
- Sumo Logic
- Supabase
- HCP Terraform
- Vultr
- Airbrake
- Codecov
Cronitor- Dynatrace
FireHydrant- Fly.io
- Honeybadger
- Akamai Linode
- Octopus Deploy
- Pulumi
- Rootly
- Semgrep
- Splunk
StatusCake- Tailscale
- Argo CD
- authentik
- Coolify
- Gitea
GlitchTip
GLPI- Jenkins
Langfuse
LibreNMS- n8n
NetBox- Portainer
- Prefect
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone- OpenAI (usage and cost)
- Anthropic (usage and cost)
- Algolia
- Flagsmith
- Unleash
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert- KnowBe4
JumpCloud
ConfigCat- Railway
- Fastly
- Postman
- Make
- Braintrust
- OpenRouter
- ElevenLabs
Split- Scaleway
Aikido Security- AssemblyAI
Astronomer- Bamboo
- Baseten
- Bitrise
- Bitwarden
- BrowserStack
- bunny.net
- Cachet
- Checkmk
- Civo
- Cloudsmith
- Codacy
- Codemagic
Comet Opik- Coralogix
CrowdStrike Falcon- Dagster+
- DeepSource
Detectify- Docker Hub
Domotz- Grafana OnCall
- Harness
- Hugging Face
- Instatus
- Koyeb
- Lambda Cloud
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary- Mezmo
NinjaOne- Nomad
Northflank- Oh Dear
- OVHcloud
Portkey- Probely (Snyk API & Web)
PromptLayer- Proxmox VE
PRTG Network Monitor- Qase
Raygun
Retell AI- Retool
Runpod- SecurityScorecard
- Semaphore CI
Shodan- SigNoz
- Socket
Squadcast- SwaggerHub
- TeamCity
Tenable- Together AI
- Travis CI
UpGuard
Uptime.com
Vanta- Vapi
- Windmill
Zenduty- OpsLevel
Cortex- Auth0
- Clerk
WorkOS
Kandji
Automox
Huntress- HackerOne
SimpleMDM- AppSignal
Healthchecks.io
Rapid7 InsightVM- 1Password Events
- JFrog Artifactory
- Sauce Labs
Zenhub- Deepgram
- Replicate
Setup
How to connect
Connect withAPI key
- 1
In the Spike dashboard, go to Settings, then API, and copy the key. It works for the whole organisation, with no scopes.
- 2
In Memtro, open Connections → Spike.sh and paste it into API key. Leave Default team id blank if the organisation has one team.
- 3
An administrator grants the actions by name, such as Create incident or Escalate, to the on-call leads who may use them.
- 4
Ask who is on call for payments 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 Spike.sh tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in Spike.sh?+
Only when you ask, and only what it has been granted: create an incident, paging the integration's escalation policy; add a note to an incident; pin a note as the incident's current state; acknowledge incidents; unacknowledge incidents; resolve incidents; escalate incidents to the next level, paging it; set the priority of incidents; set the severity of incidents; add a responder to incidents, paging them; remove a responder from incidents; add an on-call override, putting someone on call for a period; post an incident on a public status page; post a status update on a status page incident. 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 Spike.sh 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 Spike.sh 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 Spike.sh?+
API key. In the Spike dashboard, go to Settings, then API, and copy the key. It works for the whole organisation, with no scopes.
Connect Spike.sh in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.