How it works
Add OAuth credentials
Create an OAuth app in the provider (Google Console, Slack API, Notion, etc.). Add the client ID and secret to your Reminix project.
Authorize via Reminix
Reminix generates the auth URL, handles the callback, exchanges the authorization code for tokens, and stores them encrypted at rest.
Getting a token
Use the SDK or REST API to get a fresh access token for any connection.Managing connections
| Endpoint | Description |
|---|---|
GET /v1/oauth-connections | List all connections for the project |
GET /v1/oauth-connections/{name} | Get connection details |
GET /v1/oauth-connections/{name}/token | Get a fresh access token |
DELETE /v1/oauth-connections/{name} | Revoke and delete a connection |
Supported services
Connections work with any OAuth 2.0 provider. Preconfigured support is available for:Google Workspace
Slack
GitHub
Notion
Linear
Microsoft 365
Jira
Discord
HubSpot
Salesforce
Airtable
Asana
Figma
Dropbox
GitLab
Bitbucket
Confluence
Intercom
Calendly
Monday.com
Any OAuth 2.0 provider works — add the client ID and secret and Reminix handles the protocol. The list above represents providers with preconfigured defaults.
Security
- Tokens (access and refresh) are encrypted at rest
- You own the OAuth app credentials — Reminix never creates apps on your behalf
- Tokens are scoped to your project and never shared across projects
- On account deletion, all tokens and credentials are permanently destroyed