Knowledge base
Install the Zinn® GitHub app on your account or organisation and give us its installation number, so we deploy from your repositories with hour-long tokens.
Installing the Zinn® GitHub app lets a site deploy from your repositories — and a project board stay in step with GitHub — without handing us a personal token. We hold only the app's installation number, which is useless on its own, and mint a token that lasts an hour each time we need one. It is the better choice for an organisation, because it does not belong to any one person and does not stop working when someone leaves.
A GitHub account, or owner rights on the organisation where you want to install the app. Organisations that forbid third-party apps need an owner to allow it; if that is not possible, use a fine-grained token instead (Connect your GitHub account).
There is no key to create. Install the Zinn® GitHub app on your personal account or your organisation, and choose either all repositories or only the ones you want us to deploy.
Then find the installation number:
next to the Zinn® app.
the Zinn® app.
The number at the end of the address bar on that page — for example github.com/settings/installations/12345678 — is the installation number.
The app is chosen where it is used rather than on the Integrations screen:
Paste the Installation number and continue. We check the installation before saving anything; a number we cannot reach is never stored.
push deploys it.
not yours.
page — nothing needs reconnecting.
A repository is missing. The installation only covers the repositories you chose. Open Configure and add it.
The number is refused. Check it is the installation number from the address bar, not the app's own ID, and that the app is still installed — an uninstalled app has no installation.
It says the key was rejected. Almost always one of three things: a space or a line break copied with it, a key that has expired, or a key that was revoked or regenerated after you copied it. Create a fresh one and paste it again.
It connects, but something later fails. The key authenticates but lacks a permission the action needs. Create a new key with the permissions listed above, then disconnect the old connection and connect the new key.
Open Integrations, find the account and press Disconnect. That deletes the stored key at once. Anything that was using it stops at its next action, and the screens that depended on it say so rather than failing quietly.
Disconnecting does not undo what was already done — records, deployments or settings we changed on your account stay as they are. If you think the key itself may have leaked, also revoke it at the vendor; disconnecting removes our copy, not theirs.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →