GROK BOT / use-grok-bot-on-site-without-connector

Grok Bot

Use Grok Bot on a website that has no connector

Use Grok Bot on a website that has no connector

Official Bot FAQ: Grok Bot can use many browser-based tools, including services without a dedicated connector. The Bot works from a persistent cloud computer with a browser, filesystem, and terminal. Prefer a connector when one exists for a more structured integration; use the browser when no connector covers the site or when you need a visual workflow the connector does not expose.

Hand the Bot a browser task

  1. Open a one-to-one conversation with the Bot that should own the work.
  2. Name the site URL, the account or workspace to use, the outcome you want, and any approval boundary (for example: draft only; never send or publish without approval).
  3. Ask the Bot to open the site in its computer browser and complete the steps.
  4. Open Agent Computer from the conversation if you want to watch clicks and navigation.

Browser cookies and signed-in sessions persist on the shared computer, so you usually sign in once per site. Sessions expire or re-challenge on some sites; ask the Bot to pause and notify you when that happens.

Take over for human-only steps

The Bot should hand these to you and must not bypass them (FAQ + computer-and-apps):

  • Password or passkey
  • Two-factor authentication
  • CAPTCHA
  • Payment or identity check
  • A site that explicitly requires a human

Open the computer, take control, finish only the blocked step, then tell the Bot to continue. Avoid pasting passwords or one-time codes into chat. For a supported connection that presents a secure secret request, enter the value there so it stays masked and out of the conversation.

When a connector does exist

  1. Open Settings → Plugins (connectors appear as Plugins in the current app).
  2. Add the connector and finish browser authentication.
  3. In chat, type @ to attach the connector to the task.

Installed connectors are account-wide. Prefer them for supported services; keep the browser path for everything else.

Pitfalls

  • A site may block automation even when the Bot’s browser opens it — take over or change approach when the page refuses automated control.
  • Every Bot on your account shares one computer; a login you place there is available to your other Bots.
  • Do not invent connector names. Browse Settings → Plugins or grok.com/connectors for the live catalog.