Connecting other services

A connection links an outside service to your Zinn® account so the two can work together without you copying credentials around.

What can be connected

• Git providers — so a push deploys, and so boards and issues stay in step.
• Cloudflare and other DNS or CDN accounts — so we can manage records and cache on an

account you own, rather than only on ours.

• Bookkeeping tools — invoices pushed as they are issued.
• AI providers — your own key, if you would rather pay them directly than use our credits.
• Chat and alerting — where notifications should arrive.

What a connection can reach

Each one lists its scope on the connection's own row before you authorise it, and that scope is the whole of what we can do. We ask for the narrowest that works: a DNS connection can edit records on the zones you name and cannot read your billing.

Removing one

Connections → the connection → Disconnect. That revokes our access immediately. Anything that depended on it stops — a deploy hook, a DNS sync, an invoice push — and the screens that used it say so rather than failing quietly.

⛔ Disconnecting does not undo what was already done. Records we created stay, invoices already pushed stay pushed. It stops the next action, not the last one.

⭐ Use your own account where you can. A connection to your own Cloudflare or your own AI provider means the data and the billing relationship stay yours, and moving away from us later costs you nothing on that front.