Skip to main content

Integration errors

Connected apps that will not connect, show an error, or stop working after a while, with the fix for each.

What you will achieve

You will get a connected app back to working, and know when only the app's owner can fix it.

Symptoms

SymptomLikely causeFix
Connect is refused with the app's messageWrong or incomplete credentialsRe-copy the key or token from the app; check for spaces
An "OAuth" connection returns an errorSign-in was cancelled, or the account lacks the permissionTry again and approve every permission requested
It worked, then stoppedThe key was revoked, the token expired, or the password changed in the appReconnect
Works for one user, not anotherConnections are per workspace, not per personReconnect as an owner or admin
The app is connected but cannot be used in a callOnly 11 of the 19 apps can be used as in-call toolsSee Connected-app tools
"Rate limit" from the appToo many requests to the vendorWait; reduce how often the agent calls it
403 or "insufficient permissions"The key or user lacks a scopeGive the app account the required permission
Missing recordsLooking at the wrong calendar, board, base or accountCheck the identifiers you entered when connecting
Region mismatch (for example a CRM data centre)Wrong region selectedReconnect using the correct region

Per-app notes

Every app has its own page with the exact steps and the errors it commonly shows, including GoHighLevel, HubSpot, Zoho CRM, Salesforce and Slack. Start from the overview.

Testing

After reconnecting, use the integration's Test action and then a real call that uses it.

Expected result

The integration shows as connected and the test returns real data from the app.

What Phynxa cannot verify

Phynxa tests a connection by calling the app's own API with the credentials you entered. If the app changes how it works, an integration can fail until it is updated. Report the app and the exact message you see.

Something here does not match what you see in the dashboard? Let us know.