Connecting OAuth Integrations
Some integrations - Gmail, Google Drive, Microsoft Outlook, Slack, and others - use OAuth to connect your account. OAuth lets Aisle access your account without storing your password.
How to connect
- Navigate to Connectors in the main sidebar
- Find the integration you want to connect (use the filter pills to narrow by type)
- Click the connector card
- Click Connect - a popup window opens for the service's OAuth authorization page
- Sign in to the service and grant the requested permissions
- The popup closes and the connector status updates to connected
Once connected, the integration is available as a workflow node and, where supported, as an MCP tool in chat and projects.
Permissions
Each integration requests only the permissions it needs to operate. For example:
- Gmail requests permission to read and send email
- Google Drive requests permission to read and manage files
- Slack requests permission to send messages and read channel info
The specific permissions are shown on the OAuth authorization page before you confirm.
Reconnecting
OAuth tokens can expire or be revoked. If a workflow fails with an authentication error, navigate to Connectors, find the affected integration, and click Reconnect to go through the OAuth flow again.
Disconnecting
To remove a connection, open the connector from the Connectors page and click Disconnect. This revokes Aisle's access token and removes the connection from your account. Workflows using this integration will fail until the connection is re-established.
Supported OAuth integrations
| Integration | What you can do |
|---|---|
| Gmail | Read, send, and manage emails; watch for new messages |
| Google Drive | Read and manage files and folders |
| Microsoft Outlook | Read and manage email |
| Slack | Send messages, read channels, respond to events |
| GitHub | Access repositories, pull requests, and code |
| Xero | Access accounting data |
| Asana | Access projects and tasks |
For integrations not listed here that require credentials (API keys, bearer tokens), see MCP Connectors.