Integrations
Connect FanDesk to external services to bring all your data and workflows into one place.
Accessing Integrations
Go to Settings > Integrations.
Google Workspace
The Google integration unlocks Gmail, Calendar, Drive, and Contacts inside FanDesk.
What You Get
| Service | Features |
|---|---|
| Gmail | Full inbox sync, compose, reply, archive, labels, smart inbox |
| Google Calendar | Full event sync, create events, Google Meet links |
| Google Drive | Browse, search, open, and attach files |
| Google Contacts | Contact autocomplete in Mail and People directory |
Connecting Google
- Click Connect Google Account
- Sign in with your Google account
- Grant the required permissions (you can review each one before accepting)
- FanDesk begins syncing immediately
Permissions requested: Gmail read/write, Calendar read/write, Drive read-only, Contacts read. No data is sold or shared.
Multiple Google Accounts
You can connect more than one Google account:
- Click Add Another Google Account
- Sign in with the additional account
- All connected accounts appear in Mail, Calendar, and Drive
In Mail, use the account selector dropdown to switch between inboxes. In Calendar, all accounts' events appear together in one view.
Reconnecting After Expiry
Google OAuth tokens expire periodically. If your sync stops:
- Find the Google account showing "Reconnect needed"
- Click Reconnect
- Sign in and re-authorize
- Sync resumes from where it left off
Disconnecting Google
- Find the Google account in Settings > Integrations
- Click Disconnect
- FanDesk stops syncing, but your existing emails and events remain in FanDesk
- Reconnect at any time to resume sync
GitHub
The GitHub integration connects your repositories to FanDesk projects.
What You Get
| Feature | Description |
|---|---|
| Issue Sync | GitHub issues synced to FanDesk every 10 minutes |
| PR Linking | Link pull requests to FanDesk tasks |
| CI Status | See CI pass/fail status on task cards |
| Auto-Collaborators | Project members auto-invited as repo collaborators |
Connecting GitHub
- Click Connect GitHub
- You are redirected to GitHub to install the FanDesk GitHub App
- Choose your personal account or an organization
- Select which repositories FanDesk can access (you can choose all or specific repos)
- Complete the installation — you are redirected back to FanDesk
Organization Repositories
For organization repositories:
- The GitHub App must be installed on the organization (requires org admin approval)
- Once installed, all org members with FanDesk accounts can link org repos to their projects
Linking Repos to Projects
Connecting GitHub to FanDesk does not automatically link repos to projects. You must do this per project:
- Open the project settings
- Go to the GitHub tab
- Click Link Repository
- Select from your connected repositories
- GitHub issues from that repo will sync to this project
Disconnecting GitHub
- Find GitHub in Settings > Integrations
- Click Disconnect
- Linked repos are unlinked from projects
- Existing GitHub data in FanDesk is preserved but will not update
IMAP Email (Non-Gmail)
Connect non-Gmail email accounts (Zoho Mail, Outlook, Yahoo, corporate IMAP) to FanDesk:
- Click Add Email Account
- Select IMAP / Other
- Enter:
- Your email address
- IMAP server (e.g., imap.zoho.com)
- IMAP port (typically 993 for SSL)
- Username and password (or app password)
- Click Test Connection to verify
- Click Save
IMAP accounts sync your inbox and sent folders. Compose and reply are supported for IMAP accounts.
API Keys
API keys let you connect external tools and services — especially AI assistants via the MCP protocol.
Creating a Key
- Scroll to the API Keys section in Settings > Integrations
- Click Generate Key
- Enter a descriptive name (e.g., "Claude Code", "Zapier", "CI/CD")
- Click Generate
- Copy the key immediately — it will not be shown again
Key Format
FanDesk API keys use the format:
fdk_a1b2c3d4e5f6g7h8...
Key Permissions
Each key inherits the full permissions of the user who created it. Keys cannot be scoped to specific modules or read-only yet.
Security Best Practices
- Generate one key per integration (not one shared key for everything)
- Use descriptive names so you know which key is for what
- Revoke unused keys immediately
- Never commit keys to git — use environment variables instead
- Rotate keys periodically (generate new, update integration, revoke old)
Revoking a Key
Click the trash icon next to any key to revoke it. The key stops working immediately. Any integration using it will lose access.
Integration Status
Each connected integration shows:
- Connected account (email/username)
- Sync status (Active / Error / Reconnect needed)
- Last successful sync time
If an integration shows an error, click Details to see what went wrong and how to fix it.
Next: Learn about background sync in Background Sync.
Need help? Contact us at hello@fandesk.ai