Connectors let Perplexity work with your accounts in tools like Gmail, Google Drive, GitHub, Notion, Outlook, SharePoint, and many others. If a connector is misbehaving, work through the symptom that most closely matches your issue below. Each section starts with quick checks that resolve most cases, then adds targeted fixes.
Before you begin, sign in to Perplexity on the same device and browser where you first authorized the connector, and make sure you are in the correct workspace (personal, Pro, Max, or Enterprise). Many connector problems are caused by being in a different account than the one that owns the connection.
Before you start: quick checks
These four checks solve a large share of connector issues on their own. Try them first, then jump to the section that matches your symptom.
Confirm the connector is enabled in your account
Open Plugins → Installed (or Customize → Connectors if you don’t see Plugins yet) and check that the connector shows as connected. If it is missing, find its page on the Plugins page and select Connect. On Enterprise, your organization administrator controls which connectors are available — see Perplexity Connectors for Enterprise FAQ.
Reload Perplexity
Hard-refresh the page (Ctrl+F5 on Windows, Cmd+Shift+R on Mac) or restart the desktop app. Session state and connector tokens are re-read on reload.
Check your plan and platform
Some connectors and Custom MCP servers are available only on specific plans (Pro, Max, or Enterprise) or on specific surfaces (web, desktop, mobile). If a connector is missing entirely, confirm you are on a supported plan and platform.
Sign in with the right account
Perplexity connects to the third-party account you approve during the OAuth flow. If you have multiple Google, Microsoft, or GitHub accounts, sign out of the others in your browser first so you authorize the correct one.
The Installed tab shows a warning dot or a connector shows Connect
Open the Installed tab on the Plugins page. Select Reconnect next to any connector that needs it. For connectors you haven’t connected yet, open the plugin and select Connect.
A connector showing Upgrade required, Disabled by your organization, or Unavailable cannot be fixed from the plugin. For organization restrictions, see Role-based access control for connectors.
Disconnecting a connector disconnects it inside every plugin. Reconnecting it once restores the connection across all of them.
Cannot connect or authorize a connector
When you try to connect an app, the sign-in window closes, shows an error, or gets stuck before you can approve access.
Allow pop-ups and third-party cookies for perplexity.ai
OAuth relies on pop-ups and cross-site cookies. Ad blockers, strict privacy extensions, and enterprise browser policies frequently block them. Try again in a private or incognito window with extensions disabled. If it works there, allow pop-ups and cookies for perplexity.ai in your normal browser.
Sign out of other accounts on the provider
If Google, Microsoft, or the provider has multiple accounts signed in, the OAuth screen may authorize the wrong one. Sign out everywhere on the provider, then start the connector flow again and pick the account you want Perplexity to use.
Retry with a fresh flow
Go to Plugins → Installed (or Customize → Connectors if you don’t see Plugins yet), select Disconnect for the connector, wait a few seconds, and select Connect again. This forces a new OAuth handshake and clears stale tokens.
Ask your admin (Enterprise / workspace accounts)
Some Google Workspace and Microsoft Entra tenants restrict third-party apps by default. If you see “Needs admin approval”, “App is blocked”, or a similar message, your admin must approve Perplexity. See Enterprise Connector Troubleshooting Guide for the exact steps for Microsoft Entra and Google Workspace.
Connector keeps disconnecting or asking me to reauthorize
You have already connected the app, but Perplexity asks you to reconnect a few minutes or hours later.
Most reauth loops come from one of these causes:
You are signed in to more than one account on the provider. Perplexity refreshes the token for whichever session it lands in; if that session changes, the token stops matching. Sign out of the other accounts on the provider, then reconnect.
The provider password or session was reset recently. Some providers invalidate all issued tokens on a password reset, MFA change, or session revocation. Reconnect once after any such change.
Third-party cookies are blocked. Perplexity cannot silently refresh the session. Allow third-party cookies for the provider’s auth domain and for perplexity.ai.
Your admin revoked the app. On Enterprise workspaces, an admin action in Google Workspace, Microsoft Entra, or the provider’s admin console can force a reauthorization. Ask your admin whether the Perplexity app was recently removed or restricted.
If the loop continues after those fixes, select Disconnect for the connector, sign out of the provider, sign back in on the account you want, and reconnect.
A connector tool call fails, errors, or times out
When Perplexity tries to use your connected app, you see an error, the request times out, or no results come back.
Retry once
Transient provider errors and rate limits are common on the first call after a long idle period. A single retry resolves most short-lived failures.
Confirm the target still exists and you have access
If the task references a specific file, page, repository, mailbox, or spreadsheet, open it directly in the provider to confirm it is still there and that your account has permission to read or write it. Renamed folders, revoked shares, and archived items cause connector failures that look like Perplexity errors.
Check the requested action against the granted scope
Read access does not imply write access. If the task tries to modify, create, or delete something, the connector needs a write scope. Select Disconnect for the connector and select Connect again so the OAuth screen shows the full permission set, and approve every scope you need.
Wait out provider rate limits
Repeated failures with wording like “rate limit”, “quota”, “429”, or “too many requests” come from the provider throttling your account, not from Perplexity. Wait a few minutes before retrying, or split the task into smaller steps.
Perplexity says the connector is not connected, or ignores it
Your app shows as connected on the Installed tab, but Perplexity says it cannot access it or answers without using it.
Select the connector in the composer
Some surfaces require you to opt the connector in per chat or per task. Use the connector picker or an @ mention, or in Computer, type / and select the connector under Plugins.
Check your source or focus settings
If Focus, Sources, or a similar filter is set to Web-only, Academic, or Social, Perplexity will not call your connected apps. Set the source or focus to allow connectors, then retry.
Confirm the connector is scoped to this workspace or Project
Connectors authorized in your personal account are not automatically available inside an Enterprise workspace or a Project. Reauthorize the connector from inside the workspace or Project where you want to use it.
Reload and try again
Hard-refresh Perplexity, or restart the desktop app, so connector state is re-fetched. If it still shows connected but is not being used, select Disconnect and select Connect again.
The connector returns wrong, missing, or stale data
You can find the files, emails, events, or records in your app, but they are missing from Perplexity’s answer. The information it returns may also be out of date.
Confirm the data is inside the granted scope
Perplexity only sees what you authorized. Files in folders you did not share, mailboxes on a different account, and private repositories that were not selected during setup are outside scope. Reconnect and expand access if needed.
Give indexing time to catch up
For connectors that sync a corpus of files (for example, Google Drive, OneDrive, SharePoint, Dropbox, or Box), newly added items may take a few minutes to become searchable. Wait a few minutes, then hard-refresh.
Check for provider-side filters
Trash, archive, spam, and “only me” folders are typically excluded. If content lives in one of those, move or share it into a location the connector can reach.
Reauthorize to force a fresh fetch
If the data looks stuck at an old state, select Disconnect for the connector and select Connect again. This clears any cached tokens and triggers a fresh authorization.
Perplexity cannot perform a write action (send, create, edit, delete)
Perplexity can read information from your connected app, but cannot complete actions such as sending an email, creating an event, or editing a document. The action may fail, or the prompt asking you to approve it may not appear.
The connector may be authorized read-only. Select Disconnect and select Connect again, and approve every permission on the provider’s consent screen.
You may not have write permission in the target itself. Even with a write scope granted, the third-party account still needs edit or owner access to the specific file, folder, calendar, or repository.
Write approval cards must be confirmed. Perplexity asks you to approve consequential writes before they run. If you dismiss the card by accident, ask Perplexity to perform the action again.
Enterprise admins can restrict write actions. On managed workspaces, your admin may allow read but block write. Ask your admin to review the connector’s permission settings.
A connector is missing from my picker, plan, or platform
You cannot find the connector you want to use, it is greyed out, or it only appears on one of your devices.
Plan. Some connectors and Custom MCP servers are limited to Pro, Max, or Enterprise. Check the connector’s article in the Connectors & Integrations collection for its plan requirements.
Platform. A connector may be enabled on the web but not on mobile yet, or the reverse. If it works on one device and not another, the platform is the most likely cause.
Region. A few connectors are not available in every region because the provider itself is region-locked.
Enterprise policy. On Enterprise, admins choose which connectors are available to members. If a connector is missing across all your devices while it exists on other accounts, ask your admin to enable it.
Custom MCP server setup issues
Custom MCP servers let you point Perplexity at your own MCP-compliant endpoint. Most setup problems fall into a few buckets:
OAuth redirect URI is not allowlisted. Add Perplexity’s callback URL shown in the connector setup screen to your MCP server’s allowed redirect URIs, and save the change before retrying.
Server rejects Perplexity’s request headers. Confirm your server accepts standard MCP headers and does not require custom ones. If it needs a custom header, add it through Adding custom remote connectors.
Tool manifest does not refresh after an update. Select Disconnect for the connector and select Connect again to force Perplexity to re-fetch the manifest. Newly added tools appear only after the manifest is refetched.
OAuth completes but no tools show up. Confirm your MCP server exposes at least one tool and that authentication returns the token in the format your tools expect.
Local MCP on the desktop app. Local MCP servers require the Perplexity desktop app on a supported platform. If the option is missing, update the desktop app to the latest version.
Privacy, data access, and disconnection
To disconnect a connector or remove its data:
Disconnect the connector in Perplexity
Open Plugins → Installed (or Customize → Connectors if you don’t see Plugins yet) and select Disconnect for the connector. Perplexity stops making calls to it immediately.
Revoke access in the provider
In the third-party provider’s account or security settings, revoke Perplexity’s authorization. This invalidates the token even if it was cached anywhere.
Request data deletion if needed
If you also want the data that Perplexity retrieved to be removed, follow the steps in Google Drive Connector: File Upload Security and the corresponding articles for other file connectors, or contact support with your account details.
For questions about how connector data is stored and used, see Privacy & Data.
Credits were consumed when a connector failed
If a task consumed credits and the connector produced no useful result, you can ask support to review the run. Please include:
The connector name and the approximate time of the failed task.
A short description of what you asked for and what went wrong.
A screenshot of the error or the task page, if you have one.
See Subscription plans & billing and How can I contact the Perplexity team? for how to reach us.
Still stuck?
If none of the steps above resolved the issue, contact support with as much detail as you can share: the connector, the platform (web, desktop, iOS, Android), your plan, the exact error message, and a screenshot or short screen recording. That context lets us reproduce the problem and get you a fix faster. Start at Need support?.