Troubleshooting

What the errors mean when connecting an AI assistant, and how to fix them.

“MCP access is not enabled for this workspace”

What it means: the connection worked and you signed in successfully, but AI access has not been switched on for your workspace. Access is off until an admin enables it.

Fix: ask an admin to turn it on — see Enabling AI connections. Then start a new chat.

The assistant says it is not signed in, or asks you to connect again

What it means: the assistant’s access was revoked, expired, or the workspace switched AI access off.

Fix: check Settings → Connected Apps in Flow9. If Flow9 is not listed, connect again from the assistant. If it is listed and still failing, revoke it there and reconnect — that clears a stale key.

The assistant can read but refuses to change anything

What it means: your workspace is in read-only mode. Every tool that would change a record is withheld, whatever you ticked when connecting.

Fix: an admin can allow record writes — see Enabling AI connections.

”That tool isn’t available”

What it means: the tool was not ticked on the consent screen, so it was never offered.

Fix: revoke the connection in Settings → Connected Apps and connect again, ticking what you need. See Permissions.

Everything slows down or pauses part-way through a bulk request

What it means: you have hit the rate limit — 30 requests a minute. Asking an assistant to work through hundreds of records makes one request per record.

Fix: wait a minute and continue, or work in smaller batches. Normal conversation never reaches this.

ChatGPT says the connector blocked the action

Check the plugin’s permission level first. ChatGPT defaults every plugin to Allow low-risk actions, which refuses anything it judges sensitive — including creating and updating records — without asking you.

Fix: Settings → Plugins → Flow9 → Permissions, then choose Allow all actions (no prompts) or Allow read actions (asks before every change). Full explanation in Connect ChatGPT.

If permissions already allow it, this is usually ChatGPT’s own safety check, which stops the request before it ever reaches Flow9 — so nothing appears in our logs. Try again, or switch to a thinking model.

The assistant invents a status that does not exist

What it means: it guessed a stage name — “Contacted” when your pipeline uses different names.

Fix: nothing to repair. Flow9 refuses the change and replies with the list of statuses you actually use. Ask again using one of those. To see them up front:

What lead statuses can I use?

The assistant cannot find a record you know exists

Try the email address rather than the name — it is the most reliable way to find a person. If you are searching by company, ask for the account by name and then for what is linked to it.

Also check that it is looking at the right kind of record. Asking for “companies” when your workspace calls them accounts will come back empty; Flow9 suggests the right name when this happens.

Still stuck

Email [e-mail]. It helps to include which assistant you are using, what you asked, and what it replied.