Northflank logo

Northflank + Memtro

Is the API service up, and which builds failed today?

Northflank runs your services, jobs and databases, and Memtro reads it for you. It reads projects, services with build and deployment status, builds, deployments with image and commit, jobs and their runs, and database addons. When asked and granted, it can run or abort a job, pause or resume a cron schedule, and restart, pause or resume a service. It can also start or abort builds, manage databases and delete a service or job. Northflank can tell Memtro when a build fails or a container crashes, and a job can start on it. Database credentials are never read.

In Memtro

What you can do with Northflank in Memtro

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

What it does

  1. 01Reads projects, and services with their latest build and deployment status and when each changed.
  2. 02Reads builds with branch, commit and outcome, and deployments with image, tag, commit and who deployed them.
  3. 03Reads jobs with their run history, and database addons with type and status.
  4. 04When asked and granted, runs or aborts a job, pauses or resumes a cron schedule, and restarts, pauses or resumes a service. Pausing takes a live service offline.
  5. 05When asked and granted, starts or aborts a build, restarts, pauses, resumes or backs up a database, and deletes a service or job permanently.
  6. 06With events on, a failed build, a failed job run or a crashed service container can start a job.

Acts when asked

When you ask it to

These tools change something in Northflank. 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. 01Run a job now
  2. 02Abort a running job run
  3. 03Pause or resume a cron job's schedule
  4. 04Restart a service
  5. 05Pause a service (takes it offline)
  6. 06Resume a paused service
  7. 07Start a build of a service from a branch, pull request or commit
  8. 08Abort a service build
  9. 09Restart a database addon
  10. 10Pause a database addon
  11. 11Resume a paused database addon
  12. 12Back up a database addon now
  13. 13Delete a service
  14. 14Delete a job

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 Northflank for you. Each event can start a job, with the event as its input. Northflank sends a secret with every delivery, and one without it is refused.

Events and webhooks
  • 01A build started
  • 02A build succeeded
  • 03A build failed
  • 04A build was aborted
  • 05A service deployment changed status
  • 06A service scaled automatically
  • 07A job run started
  • 08A job run succeeded
  • 09A job run failed
  • 10A job run was aborted
  • 11A job run was terminated
  • 12A database backup started
  • 13A database backup succeeded
  • 14A database backup failed
  • 15A database backup was aborted
  • 16A service container crashed
  • 17A service container was evicted
  • 18A job container crashed
  • 19A database container crashed
  • 20A database volume passed 90% full
  • 21A release flow run failed
  • 22A template run failed
  • 23A preview environment run failed
  • 24An invoice payment failed
  • 25A billing alert threshold was passed
In practice

Ask it like you would a colleague

Once Northflank 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.

Northflank logoNorthflank + Memtro
  • Is the API service deployed and running?

  • Which builds failed today?

  • When did the nightly import job last succeed?

  • Which databases in the production project are paused?

  • Restart the worker service.

01

What shipped yesterday

Maya Okafor, engineering manager at Acme Ltd, asked what was deployed to production yesterday. Memtro listed each deployment with its service, commit message, image tag and who deployed it.

02

A crashed container

When Northflank told Memtro a service container had crashed at Northwind, a job started. It read the service's recent deployments and builds and posted them to Dan Fletcher, the on-call engineer.

Teams

Where it fits

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

Better together

Works with

A record in Northflank 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 token, plus Team ID for organisation tokens
  1. 1

    In Northflank, go to Team settings, then API, then Tokens. Create an API role with the read, update and delete permissions Memtro should have, then create a token with that role.

  2. 2

    In Memtro, open Connections → Northflank and paste the API token. For an organisation token, also enter the Team ID.

  3. 3

    An administrator grants the service, job, build and database actions by name to the engineers who may use them. Events are turned on from the connection's Events tab.

  4. 4

    Ask which builds failed today.

Also works from

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

FAQ

Questions

Can Memtro change anything in Northflank?+

Only when you ask, and only what it has been granted: run a job now; abort a running job run; pause or resume a cron job's schedule; restart a service; pause a service (takes it offline); resume a paused service; start a build of a service from a branch, pull request or commit; abort a service build; restart a database addon; pause a database addon; resume a paused database addon; back up a database addon now; delete a service; delete a job. 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 Northflank 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 Northflank 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 Northflank?+

API token, plus Team ID for organisation tokens. In Northflank, go to Team settings, then API, then Tokens. Create an API role with the read, update and delete permissions Memtro should have, then create a token with that role.

Can Northflank 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 Northflank 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 Northflank 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