Skip to content

Unofficial community registry. Not affiliated with, endorsed by, or sponsored by xAI.

中文

Guides

A connector that will not connect

connector-wont-connect

A connected badge can still miss the permission this run needs. Match the scope in the entry, not the green light.

for Grok Bot · unofficial, not affiliated with xAI

CNPS0.1.02026-11-18New

Paste this note into Grok Bot and say: follow this note.

Note: A connector that will not connect
A connected badge can still miss the permission this run needs. Match the scope in the entry, not the green light.

For: People whose routine stops on a connector, or who can connect and still cannot read mail, a sheet, or notes.

What to check:
1. Separates a failed authorization, a scope that is too small, and a read that returns empty.
2. Asks you to name the action you need: read, or draft.
3. Refuses “all permissions” as the way to make one run pass.

Steps:
1. Copy the error as it was written, including the sentence from the other system. “It will not connect” is not the error.
2. Open the connector entry here. The mail task must read and draft, and must not send. The Gmail app can still send.
3. Write the task rule next to what the app can actually do. Tell the task not to send. The docs do not say the sign-in screen can turn send off.
4. Retry with a read-only probe, such as the subjects of five recent messages and no bodies. If that fails, stop. Do not ask for every permission.

Connector:
Scope the entry asks for:
Scope actually granted:
Last error, verbatim:

Do not:
- Do not paste authorization codes, refresh tokens, or client secrets into a skill or a chat.
- Do not grant every permission because a connection failed.
- Do not search for an app named “CRM (read only)” or “Public DNS lookup.”

Paste this note into Grok Bot and say: follow this note.

What it does

  • Separates a failed authorization, a scope that is too small, and a read that returns empty.
  • Asks you to name the action you need: read, or draft.
  • Refuses “all permissions” as the way to make one run pass.

Who it is for

People whose routine stops on a connector, or who can connect and still cannot read mail, a sheet, or notes.

How to put it in Grok Bot

  1. Copy the error as it was written, including the sentence from the other system. “It will not connect” is not the error.
  2. Open the connector entry here. The mail task must read and draft, and must not send. The Gmail app can still send.
  3. Write the task rule next to what the app can actually do. Tell the task not to send. The docs do not say the sign-in screen can turn send off.
  4. Retry with a read-only probe, such as the subjects of five recent messages and no bodies. If that fails, stop. Do not ask for every permission.

Example

Four lines to compare

Connector:
Scope the entry asks for:
Scope actually granted:
Last error, verbatim:

Connectors it needs

No connector.

Safety and permissions

  • Do not paste authorization codes, refresh tokens, or client secrets into a skill or a chat.
  • Do not grant every permission because a connection failed.
  • Do not search for an app named “CRM (read only)” or “Public DNS lookup.”

Risk: Low

Questions

It worked yesterday.

Check whether the grant expired and whether the other system renamed a scope. Match the error text before you rewrite the skill.

The test account works and the real mailbox does not.

Grants are often per account. Check the account that failed. Do not assume an organization grant covers it.