FanDesk

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

ServiceFeatures
GmailFull inbox sync, compose, reply, archive, labels, smart inbox
Google CalendarFull event sync, create events, Google Meet links
Google DriveBrowse, search, open, and attach files
Google ContactsContact autocomplete in Mail and People directory

Connecting Google

  1. Click Connect Google Account
  2. Sign in with your Google account
  3. Grant the required permissions (you can review each one before accepting)
  4. 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:

  1. Click Add Another Google Account
  2. Sign in with the additional account
  3. 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:

  1. Find the Google account showing "Reconnect needed"
  2. Click Reconnect
  3. Sign in and re-authorize
  4. Sync resumes from where it left off

Disconnecting Google

  1. Find the Google account in Settings > Integrations
  2. Click Disconnect
  3. FanDesk stops syncing, but your existing emails and events remain in FanDesk
  4. Reconnect at any time to resume sync

GitHub

The GitHub integration connects your repositories to FanDesk projects.

What You Get

FeatureDescription
Issue SyncGitHub issues synced to FanDesk every 10 minutes
PR LinkingLink pull requests to FanDesk tasks
CI StatusSee CI pass/fail status on task cards
Auto-CollaboratorsProject members auto-invited as repo collaborators

Connecting GitHub

  1. Click Connect GitHub
  2. You are redirected to GitHub to install the FanDesk GitHub App
  3. Choose your personal account or an organization
  4. Select which repositories FanDesk can access (you can choose all or specific repos)
  5. 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:

  1. Open the project settings
  2. Go to the GitHub tab
  3. Click Link Repository
  4. Select from your connected repositories
  5. GitHub issues from that repo will sync to this project

Disconnecting GitHub

  1. Find GitHub in Settings > Integrations
  2. Click Disconnect
  3. Linked repos are unlinked from projects
  4. 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:

  1. Click Add Email Account
  2. Select IMAP / Other
  3. Enter:
    • Your email address
    • IMAP server (e.g., imap.zoho.com)
    • IMAP port (typically 993 for SSL)
    • Username and password (or app password)
  4. Click Test Connection to verify
  5. 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

  1. Scroll to the API Keys section in Settings > Integrations
  2. Click Generate Key
  3. Enter a descriptive name (e.g., "Claude Code", "Zapier", "CI/CD")
  4. Click Generate
  5. 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