Connected Accounts
Manage OAuth connections to Gmail, Outlook, GitHub, Google Calendar, and other integrations.
Connected Accounts
Connect Workestra to your favorite tools and services for seamless workflows.
Screenshot needed � add an annotated image showing this UI
Managing Connections
View all your connected accounts at Settings > Connected Accounts.
Connection List
Each connected account shows:
| Information | Description |
|---|---|
| Service | Provider name and icon |
| Account | Connected email/username |
| Status | Connected, Expired, Error |
| Connected On | When the connection was established |
| Last Used | Most recent activity |
Supported Integrations
Connect your email accounts to send and receive emails directly in Workestra.
Gmail
What it enables:
- Send emails from your Gmail address
- Receive replies in Workestra Inbox
- Email tracking (opens, clicks)
- Contact sync
Permissions requested:
- Read, send, and modify emails
- View email metadata
- Manage email labels
Outlook / Microsoft 365
What it enables:
- Send emails from your Outlook address
- Real-time two-way email sync
- Reply and forward from Workestra
- Automatic CRM linking
- Azure AD SSO support
Permissions requested:
Mail.Read� Read emails from your inboxMail.ReadWrite� Manage read/unread statusMail.Send� Send emails on your behalfUser.Read� Read your profileContacts.Read� Sync contacts for CRM matchingCalendars.Read� Calendar events (future feature)offline_access� Maintain sync without frequent re-auth
Enterprise features:
- Azure AD Single Sign-On (SSO)
- Multi-Factor Authentication (MFA)
- Conditional Access policy support
- Organization-wide admin consent
? Microsoft 365 Integration Details
The Microsoft 365 integration uses OAuth 2.0 with PKCE and AES-256-GCM encryption for maximum security. Your credentials are never stored.
Developer Tools
GitHub
What it enables:
- Import documentation to Knowledge Base
- Link issues to Projects (if implemented)
- Sync repository activity
Permissions requested:
- Read repositories
- Read repository contents
Calendar
Google Calendar
What it enables:
- View calendar availability when scheduling
- Create events from Workestra
- Sync meeting invitations
Permissions requested:
- calendar.readonly
- calendar.events
Automation
Zapier
What it enables:
- Connect Workestra to 5,000+ apps
- Create automated workflows (Zaps)
- Trigger actions based on Workestra events
Setup:
- Generates API key with
wkz_prefix - Use key in Zapier's Workestra integration
Finance
Stripe
What it enables:
- Payment processing
- Subscription billing
- Invoice sync
- Webhook event handling
Permissions:
- Read payment data
- Create charges
- Manage subscriptions
Banking
Connect bank accounts for automatic transaction sync:
| Provider | Coverage | Features |
|---|---|---|
| Plaid | US, CA, GB, FR, ES, NL, IE | Real-time sync, reconciliation |
| Salt Edge | EU, UK, Global | Multi-country support |
| Tink | 18 EU countries | 6,300+ banks |
| Ponto | Belgium/Benelux | European focus |
Monitoring
Sentry
What it enables:
- Error tracking integration
- Application monitoring
- Performance insights
Setup:
- Enter Sentry auth token (format:
sntryu_...) - Auto-detects organization
Other AI Providers
OpenAI
What it enables:
- Module-specific AI features
- Different from workspace AI settings
Setup:
- Enter OpenAI API key
- Configure per-module usage
Connecting a New Account
Step-by-Step
- Go to Settings > Connected Accounts
- Click Connect Account
- Select the service you want to connect
- Complete the OAuth flow
- Grant requested permissions
- Return to Workestra
OAuth Flow
Workestra uses industry-standard OAuth 2.0:
- You click Connect
- You're redirected to the provider (Google, Microsoft, etc.)
- You sign in (if not already)
- You review and approve permissions
- You're redirected back to Workestra
- Connection is established
Workestra never sees your password for connected accounts. We only receive an access token with the permissions you explicitly grant.
Microsoft 365 Connection Flow
Connecting Microsoft 365 follows a specific flow for enterprise security:
Click "Connect Outlook"
?
Review permissions modal
?
Redirect to Microsoft sign-in
?
Enter email + password
?
Complete MFA (if enabled)
?
Review app permissions
?
Click "Accept"
?
Redirect back to Workestra
?
Initial sync beginsIf your organization requires admin consent, you'll see a message asking you to contact your IT administrator.
Reconnecting Expired Accounts
OAuth tokens expire periodically for security. When this happens:
- The account shows Expired status
- Click Reconnect
- Complete the OAuth flow again
- Service is restored
Some providers (like Google) require reconnection every 6 months. Set a calendar reminder to avoid interruptions.
Revoking Access
From Workestra
To disconnect an account:
- Find the account in Connected Accounts
- Click Disconnect or Revoke
- Confirm the action
What happens:
- Connection is immediately severed
- Data synced from the service remains
- New data stops flowing
From the Provider
You can also revoke access from the provider's side:
- Google: myaccount.google.com/permissions
- Microsoft: account.live.com/consent/manage
- GitHub: Settings > Applications > Authorized OAuth Apps
Revoking from the provider side will cause errors in Workestra. We recommend disconnecting from Workestra first.
Connection Troubleshooting
"Connection Failed" Error
- Check that you're signed into the correct account
- Verify you granted all requested permissions
- Try incognito/private browser mode
- Clear cookies and try again
"Token Expired" Repeatedly
Some providers have short token lifetimes:
- Reconnect the account
- Check for provider-specific issues
- Contact support if the issue persists
"Admin Consent Required" (Microsoft 365)
Your organization requires IT administrator approval:
- Contact your IT admin
- Ask them to approve "Workestra" app in Azure AD
- Alternatively, they can use the admin consent URL
- Retry connection after approval
Permissions Denied
If you denied permissions during OAuth:
- Disconnect the partial connection
- Reconnect and grant all requested permissions
- Some features won't work without full permissions
Security & Privacy
Data Access
Workestra only accesses the data necessary for the integration:
- Email: Messages and metadata for Inbox sync
- GitHub: Repository contents for documentation import
- Calendar: Events for scheduling features
Data Storage
- OAuth tokens are encrypted at rest (AES-256-GCM)
- Tokens are never logged or exposed in the frontend
- Data is stored only as long as the connection is active
Token Security Details
| Aspect | Implementation |
|---|---|
| Encryption Algorithm | AES-256-GCM |
| Key Management | Environment-based, rotated regularly |
| Token Refresh | Automatic before expiry |
| Failed Refresh | Auto-deactivate after 10 failures |
| Cookie Security | httpOnly, Secure, SameSite=Lax |
Third-Party Access
Workestra does not:
- Sell your data to third parties
- Use your data for advertising
- Train AI models on your private data
Next Steps
- Email Integration � Deep dive into email connections
- Microsoft 365 Setup � Detailed Outlook/Office 365 guide
- GitHub Integration � Sync documentation
- Security Settings � Manage account security