Integrations
The Integrations page registers the external applications that exchange data with Windshift. It has two directions.
Outbound
An outbound provider holds the OAuth credentials Windshift uses to read data from an external service, such as Notion or Confluence. Add the provider once, then Windshift connects on behalf of the instance.
- Open Admin, then Integrations.
- Select the Outbound direction.
- Select Add Provider.
- Enter a name, slug, and the OAuth client credentials.
- Save the provider.
Inbound OAuth clients
An inbound OAuth client registers a third-party app that authorizes Windshift users with OAuth 2.0 and PKCE. The app receives per-user API tokens that inherit the user's permissions, limited to the scopes you allow.
- Select the Inbound direction.
- Select Register Client.
- Enter the display name, slug, and client type.
- Add one redirect URI per line. The authorization request must match one exactly.
- Select the allowed scopes.
- Save the client.
A confidential client stores a client secret on the server. A public client uses PKCE only. Rotate a client secret when it may be exposed. The previous secret stops working immediately and existing tokens keep working until they expire. Deleting a client revokes all access and refresh tokens issued to it.
Related documentation
- SCM Integrations for repository connections.
- Actions for automations that call external services.