Connect GitHub to your Zuuna board
Commits, branches, pull requests and build status from GitHub land on the right card automatically. How to connect it — and what it does not do.
Integrations
Connect the board to where the work happens
The connection that matters most is the one to your code: commits, branches, pull requests and build status land on the right card without anyone retyping anything. Beyond that there are signed webhooks and a REST API for everything that has no page of its own here.
All integrations
Connect GitLab to your Zuuna board (self-hosted included)
GitLab.com or your own instance behind the firewall: an address, a project path and a token that is never stored. How the connection works.
Connect Gitea or Forgejo to your Zuuna board
For your own Gitea or Forgejo instance: an address, a repository and a token used once and never stored — including instances with no route in from outside.
Self-hosted is the normal case, not the exception
For GitLab and Gitea you give the address of your own instance and issue your own token. That is why an instance reachable only from inside your network still works: Zuuna tries to register the webhook automatically, and when it cannot — because the instance is not reachable from outside — it hands you the URL and the secret to enter yourself. The connection is then made from your side.
The token is used once and not stored. What remains is the mapping from repository to group, and the webhook secret, which is kept encrypted.
When there is no page for it
Then webhooks and the REST API. Zuuna posts signed events to any URL you
register and accepts changes through /api/v1. Zapier, Make
and n8n need nothing beyond that — a token, a URL, and the events you
care about.
Connecting takes longer to read about than to do.
Link a repository, write a commit mentioning a card ID, done. 14 days of full access, no credit card.