Skip to main content
Most connector problems come from the assistant plan, the workspaces selected during connection, the permissions approved, your current Chatobserver role or a capability that is not yet exposed through MCP.

​
I cannot add the connector in Claude

Check that your Claude plan supports custom connectors. On Team or Enterprise, ask an Owner or Primary Owner to add Chatobserver under Organization connectors; individual members cannot add the organisation connector themselves.

​
I cannot add the connector in ChatGPT

Custom connectors currently require an eligible ChatGPT workspace and must be enabled and published by an Admin or Owner. Confirm that you are using the web workspace where the connector was added.

​
No Chatobserver workspace is available

Confirm that you signed in with the intended Chatobserver account and have an active membership in a current, eligible workspace. Archived or expired workspaces are not offered. If the wrong account was used, cancel and begin the connection again.

​
The assistant asks me to choose a workspace

The connection has access to more than one workspace. Choose by its readable name. The assistant should not make you identify it from a long internal ID. For a tighter boundary, revoke the connection and reconnect with only the intended workspace selected.

​
A change action is missing or denied

Possible causes include:
  • the connection only has read permission;
  • your current workspace role cannot make that change;
  • the workspace plan or prompt allowance prevents it;
  • a required workspace feature is unavailable; or
  • the action is outside the current connector scope.
Reconnect and approve additional access only if you actually want the assistant to make changes.

​
Tracked coverage is missing

Reconnect Chatobserver so the connection can request the newer Tracked coverage read and change permissions. The workspace must also have Tracked coverage available in the Chatobserver Sources area. If the feature is unavailable in the app, the connector will not bypass that workspace setting. Tracked coverage is not the same as source-domain tracking or group coverage. Ask specifically for “Tracked coverage” and provide the published page URL when you want to save or measure an article, interview, podcast or PR placement.

​
Reports, alerts, billing or integrations are missing

The connector does not currently manage reports, alerts, billing, subscriptions, workspace members, developer credentials or integration setup. Use the Chatobserver app for those tasks.

​
A grouping rule did not move existing prompts

Grouping rules currently apply prospectively and do not reorganise existing prompts. Ask the assistant to add or remove the existing prompts from the group directly.

​
The connector asks me to reconnect

Connections expire after 30 days and stop immediately when revoked. Reconnect from the assistant and complete the Chatobserver consent flow again. Reconnect after newly supported permissions are added if you want the assistant to use them. Existing approval does not automatically expand.

​
The approval prompt contains JSON

Claude, ChatGPT and other assistants decide how approval details are displayed. JSON can be normal, but every workspace-scoped request should include the readable workspace name. Deny it if the workspace or proposed action is not what you expected.

​
The assistant reports only part of a result

Some lists and evidence tables continue through multiple pages. Ask the assistant to retrieve every page, or narrow the filters. Competitor-review changes can also return a mixture of applied items and conflicts; ask the assistant to report each status rather than summarising the whole review as successful.

​
A prompt run is not visible yet

Ask the assistant to check collected answers for the selected prompt. Do not approve another run merely to see whether the first request completed, because each new run can consume allowance.