Connector Overview
The common architecture behind every real PawOS connector.
A connector is a real integration with an external provider, authenticated through real OAuth where the provider supports it, behind one common ConnectorSDK interface — no per-provider special-casing in how PawOS decides whether an action is allowed.
OAuth token exchange happens on PawOS’s backend, not inside the desktop app, so client secrets are never shipped to or stored on your machine.
Note
Connecting most integrations currently requires the relevant connect* entitlement — see the tier note on each connector page.
How it works
What you see
- Connection setup, connected/disconnected status, permission screens from each service, and approval questions for actions.
- Each connector page lists exactly what that connection can do.
What PawOS does
- PawOS uses your connected account only for the actions that connector supports.
- Sign-in is handled securely, and PawOS asks for extra access only when a feature needs it.
- Connectors that need a higher plan stay locked until your plan includes them.
Permissions
- Connecting an account does not approve future actions — comments, deploys, rollbacks and other changes still ask first.
- If a connection is missing, expired or lacks access, PawOS tells you instead of continuing.
Records
- Connector actions record the service, the result, and any error the service returned.
Good to know
- Service settings and permissions vary, so the same request can behave differently for different accounts.
Related