Connect Netlify to ShipVitals
Sites, production deploys, bandwidth and build minutes, and the plan's estimated cost
BetaKey, not read-only · about 2 minutes
Beta: this connector is new in the beta, and we're still checking it against more accounts.
What it reads
- Personal access token
- Lists the team's sites and production deploys, and reads bandwidth and build minutes
Not read-only at Netlify. Netlify's tokens can't be limited to reading: one can also deploy and change sites in every team you belong to. ShipVitals only reads sites, deploys, bandwidth and build minutes.
What ShipVitals keeps: The access token, encrypted, and the team slug if you enter one.
How to connect
- In Netlify, open User settings → Applications → Personal access tokens.
- Create a new token named ShipVitals, with an expiration you're happy to renew.
- Copy the token. Netlify shows it once.
About 2 minutes.
How to revoke
Removing the connection in ShipVitals deletes the stored key at once.
What it powers
Dashboard tabs: Costs, Health.
Figures it fills
- Bandwidth this billing period
- Build time this billing period
Sync
- Free: Daily
- Indie: Hourly
- Studio: Every 15 minutes
- Agency: Every 15 minutes
Netlify reports a day in full after 1 day; ShipVitals waits for it.
Troubleshooting
Each error a connection can hit, and its fix. The connection's health page names the one it hit.
- Access refused
- Netlify didn't accept the token: it may have expired, been deleted, or a password reset revoked it. Create a new one and paste it.
- A permission is missing
- Netlify refused part of the team's data. A team on SAML single sign-on needs a token created with access to it.
- Access removed
- ShipVitals' access was removed in Netlify. Connect it again; the history it brought in is kept.
- Rate-limited
- Netlify is limiting this token's requests (500 a minute, shared with your other tools). ShipVitals tries again shortly.
- Quota reached
- The account used up a Netlify quota. The sync resumes when the quota resets.
- Not found
- Something the connection reads is gone from Netlify: renamed, moved or removed. Review the connection's resources, or connect again.
- Netlify is unavailable
- Netlify is having trouble on its side. Check its status page; ShipVitals retries by itself.
- Couldn't reach Netlify
- The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that Netlify is reachable.
- An answer ShipVitals didn't expect
- Netlify 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
- Netlify needs to know which team to read: enter the team's slug from its URL.