What is documented

Grok Bot supports structured connectors, presented as Plugins, alongside browser work. Official guidance prefers a connector where available and uses the browser for unsupported services or visual work. Connections and signed-in sessions belong to the shared account environment, rather than being isolated to one Bot.

The comparison procedure below is our editorial method. We have not verified any particular connector's current action coverage.

Documentation: Official computer and apps guide ↗

Choose by action, not by app name

A connector for a service may expose search but not the export, filter, or historical records your task needs. Write the operation first: retrieve this account's open tickets, including their latest replies and timestamps. Then check whether the available tool can perform that operation under the account you intend to use.

A browser may be the practical choice for checking layout, reviewing a chart, or handling an unsupported screen. It also adds page state to the problem: selected account, filters, open dialogs, and pagination can change the result. Record these details in the task rather than assuming the default screen is correct.

  1. Name one required read operation and the fields the result must contain.
  2. Check the available connection's documented or displayed actions and requested access.
  3. Authorize only the account and scope needed for the pilot.
  4. Run a small read and compare it with the same records in the source application.
  5. If browser work is necessary, specify the account, filters, date range, and a stopping point before any write.

Probe access without expanding the task

Successful authentication is only the beginning. The useful test is whether the intended records and fields can actually be read.

Try this brief

For [service/account], establish whether you can read [specific records and fields] using the available connector. Read only [small sample]. Return the source links or IDs, applied filters, retrieval time, and missing fields. Do not create, edit, send, or delete anything. If the connector cannot perform this operation, explain the exact gap and propose the smallest browser-based check. Ask me to complete any required sign-in securely.

Original editorial template. Replace placeholders and review access before running.

Leave a short access note

Keep a note beside the workflow containing the connection used, permitted action, account, successful sample, and last test date. This turns a future 'it stopped working' report into a narrower question: did access expire, did action coverage change, or did the source move?

Do not broaden privileges merely to make an inconvenient task pass. First determine which missing action or record caused the failure. The note should describe access, never contain passwords or secret values.

  • The sample matches the source application.
  • All required fields are present, or omissions are explicit.
  • The method handles more than the first page of results when completeness matters.
  • The workflow has a clear sign-in or missing-access stopping point.

Sources & next steps

Capabilities are grounded in the documentation below. The workflow design and acceptance checks are editorial suggestions.

Build your own workflow brief ↗