Documentation

Troubleshooting

Start with connection status. Never repeat a possible change with a new ID before checking what happened.

Custom MCP connection · not yet listed or officially approved in the ChatGPT or Claude directory.

Missing login or permission · 401 / 403

401 means valid access is missing. Sign in again through your assistant’s connection. 403 can mean missing permission, an inactive connection or workspace access. Check consent and your selected account. Never share tokens with support.

“Reconnect” or an older-connection message: add the connection again and approve the required permissions. New tools being listed does not give old grants new access.

No deals or missing mail

Check workspace, search filters and whether the deal is visible and confirmed. frida_search_deals defaults to active; closed or all requires expanded access. Mail evidence may be partial or awaiting sync. No observed sent message does not prove you never replied.

Deal or receipt unavailable · 404

An ID may belong to another workspace, have been deleted or be outside your access. A receipt may be unavailable or older than 24 hours. Search again in the correct account. Absence is not evidence that a change happened.

Conflicting change · 409

If the deal changed since you read it, read it again and reconsider. A request_id already used for different input must not be reused for a new intent. An unchanged value or stage can also be rejected as unnecessary.

Undo can fail when the field has changed since. Do not overwrite newer work to force an undo. Inspect the current state in Frida.

Invalid input · 422 or tool error

Check the input schema: UUIDs, date ranges, allowed stages and exactly the field matching action. Notes with instruction markers or structural tags can be rejected. Shorten a note if existing notes are full. MCP may return validation and domain failures as tool errors even with HTTP 200.

Too many requests · 429

Wait as instructed and respect Retry-After when present. The edit limit may require waiting until next hour. Repeated automatic retries will not help. Limits and page sizes are documented in the reference; access is not promised to be unlimited.

Timeout after a change

For frida_update_deal, look up status with the original request_id. A retry must reuse that ID and identical parameters; a new ID may create another change. This guarantee does not cover every write tool. Check state before repeating other actions.

Send useful diagnostic information

Contact support with time and time zone, assistant name, tool name, error text and request_id or change_id if available. Describe the workspace without sharing passwords, tokens or mail content.

Find your next step