BusyBot
Search all guides

Reference · Credentials

Connect Grist to BusyBot

Used by 1 BusyBot node.

Type gristApi 4 fields

Fields

FieldTypeRequiredNotes
API Key
apiKey		 password Yes —
Plan Type
planType		 options Yes —
Custom Subdomain
customSubdomain		 string No For paid plans (e.g., myteam for myteam.getgrist.com).
Self-Hosted URL
selfHostedUrl		 string No http://localhost:8484

Setting up Grist API

  1. In Grist API, create the credential this connection needs — the values listed in the table above. These are issued from your own Grist API account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose Grist API.
  3. Paste each value into the matching field and save.
  4. Add the Grist node to a workflow, select this credential, and run a simple operation to confirm it authenticates.

Security

  • Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
  • Grant the minimum scopes or permissions the operations you actually use require.
  • Rotate the credential periodically, and immediately if it may have been exposed.
  • Credentials are scoped to your account — a workflow cannot use another account's.

Frequently asked questions

Which BusyBot nodes use Grist credentials?

One node: Grist. Create the credential once and select it in that node.

What does a Grist credential need?

4 fields: API Key, Plan Type, Custom Subdomain, Self-Hosted URL. Required: API Key, Plan Type. The values come from your own Grist account.

How are Grist secrets stored?

Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.

Nodes that use Grist API

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