BusyBot

Reference · Credentials

xAI credentials

Used by 13 BusyBot nodes.

Type xai 2 fields

The xAI credential holds an API key for Grok models and unlocks 13 BusyBot nodes — chat, reasoning, structured output, vision, image and video generation, web and X search, and collections. Create the key once in the xAI console and every Grok node can use it.

Fields

FieldTypeRequiredNotes
API Key
apiKey		 password Yes Your xAI API key from console.x.ai
Base URL
baseUrl		 string No Override the xAI API base URL (for proxies or custom endpoints)

Getting your credentials

  1. Sign in to the xAI console at console.x.ai.
  2. Create an API key from the API keys area of the console.
  3. Copy the key and paste it into the credential’s API Key field.
  4. Leave Base URL empty unless you are routing through a proxy or a custom endpoint — the node uses xAI’s default endpoint when it is blank.

Permissions and scopes

The key carries the access of the account and team it belongs to. Usage and billing are tracked against that account, so create the key under the team whose budget should carry it.

The optional Base URL exists for proxying or self-managed gateways. Only set it if you know the endpoint is API-compatible with xAI.

Troubleshooting

  • 401 Unauthorized — the key is wrong or revoked. Create a new one in the console and update the credential.
  • Model not available — the selected model may not be enabled for your account. Choose another from the node’s Model dropdown.
  • Requests going somewhere unexpected — check whether Base URL has been set. An incorrect override sends every request to the wrong host while the key itself is fine.

Frequently asked questions

What is the Base URL field for?

Overriding the xAI API endpoint for proxies or custom gateways. Leave it empty for normal use — a wrong value sends every request to the wrong host even though the key is valid.

Does one key cover all the Grok nodes?

Yes. All 13 xAI nodes — chat, reasoning, vision, image, video, search and collections — use this single credential type.

Is an X Premium subscription enough?

No. API access through console.x.ai is separate from consumer Grok access, so the API account needs its own setup and billing.

Where do I see usage?

In the xAI console against the account the key belongs to, which is why creating it under the right team matters.

Nodes that use xAI

One credential works across every node below — create it once and reuse it.

Last updated . Spotted something wrong? Tell us.