Skip to content

All integrations

Connect Neon to ShipVitals

Compute, storage and transfer per project, and the plan's cost

AvailableKey, not read-only · about 2 minutes

Connect Neon

What it reads

Organisation API key
Reads projects and consumption

Not read-only at Neon. Neon has no read-only key; ShipVitals only reads projects and consumption.

What ShipVitals keeps: The API key, encrypted, and the plan price you enter.

Every connector's scopes, on one page

How to connect

  1. Open Account settings → API keys in the Neon Console.
  2. Create a key named ShipVitals.
  3. Copy the key. It starts with napi_.

About 2 minutes.

Open Neon

How to revoke

Removing the connection in ShipVitals deletes the stored key at once.

What it powers

Dashboard tabs: Costs.

Figures it fills

  • compute.seconds
  • compute.seconds.cycle
  • storage.bytes
  • storage.written_bytes
  • transfer.bytes
  • transfer.bytes.cycle
  • quota.compute.share

Sync

  • Free: Daily
  • Indie: Hourly
  • Studio: Every 15 minutes
  • Agency: Every 15 minutes

Troubleshooting

Each error a connection can hit, and its fix. The connection's health page names the one it hit.

Access refused
Neon no longer accepts what ShipVitals signs in with. Create a new key, or connect again, and replace it in the connection.
A permission is missing
What ShipVitals has can't read everything it needs. Add the permissions under What it reads, or create a new key with them, and test again.
Access removed
ShipVitals' access was removed in Neon. Connect it again; the history it brought in is kept.
Rate-limited
Neon asked ShipVitals to slow down. Nothing to do: the sync carries on by itself and catches up.
Quota reached
The account used up a Neon quota. The sync resumes when the quota resets.
Not found
Something the connection reads is gone from Neon: renamed, moved or removed. Review the connection's resources, or connect again.
Neon is unavailable
Neon is having trouble on its side. Check its status page; ShipVitals retries by itself.
Couldn't reach Neon
The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that Neon is reachable.
An answer ShipVitals didn't expect
Neon answered in a shape ShipVitals didn't expect, usually after a change on its side. We're told, and the data you have is kept.
A setting doesn't work
A field in the connection doesn't work with Neon. Check it against How to connect, and test again.

Docs