Managing connections
Reconnecting expired grants, sharing, auto-wire defaults, and what happens to workflows when you disconnect.
Everything lives in Settings → connectors: click a connected provider to open its panel.
When a connection expires
OAuth grants can lapse (revoked on the provider side, expired refresh). The connection flips to reconnect needed — an amber badge in Settings and on any step picker using it — with a reconnect button that re-runs the OAuth dance into the same connection. Nothing needs rewiring: every step bound to it works again the moment reconnect finishes.
That's also the rotation story for API keys: reconnecting replaces the secret in place.
Defaults for auto-wire
Each connection panel has a Defaults editor — a small JSON map of fields auto-filled whenever the AI wires this connection into a step (a default channel, a default repo). Edit it once; every future build inherits it.
Disconnecting
disconnect removes the connection after a confirmation that says exactly what happens: workflows using this connection will stop running until you reconnect. Steps keep their binding and fail at run time with a clear "configuration not found" — nothing is silently rewired. Reconnecting the provider creates a new connection, so plan to re-bind affected steps (or let the AI's post-connect wiring re-apply the one-connection rule).
Security notes
- Credentials are encrypted at rest and never rendered back into any UI — not to you, not to the AI.
- At run time, a step's connection is loaded through the workspace scope of the execution — a binding that points outside your workspace simply doesn't resolve. Cross-tenant use is structurally impossible, not just forbidden.