BusyBot

Reference · Credentials

SeaTable API credentials

Used by 2 BusyBot nodes.

Type seaTableApi 4 fields

The SeaTable credential holds an API token scoped to a single base, plus settings for where your instance lives. The token is per base rather than per account, so a workflow spanning two bases needs two credentials.

Fields

FieldTypeRequiredNotes
Environment
environment		 string No Deployment type: "cloudHosted" or "selfHosted"
Domain
domain		 string No Base URL of your SeaTable instance
API Token (of a Base)
token		 password Yes The API token of the SeaTable base to access
Timezone
timezone		 string No SeaTable server timezone (e.g., Europe/Berlin)

Getting your credentials

  1. Open the SeaTable base you want the workflow to use.
  2. In the base’s settings, create an API token for it, naming it for this integration.
  3. Copy the token into the credential’s Token field.
  4. Set Environment to cloudHosted or selfHosted.
  5. For a self-hosted instance, set Domain to its base URL. Cloud instances use the default.
  6. Set Timezone to the SeaTable server’s timezone, for example Europe/Berlin. Date values are interpreted against it.

Permissions and scopes

A base API token reaches only that base — which is a useful property. Give each workflow a token for the base it needs rather than sharing one broadly.

Troubleshooting

  • 401 or 403 — the token belongs to a different base, or was revoked in the base’s settings.
  • Connection failures on self-hosted — the Domain is wrong, or the instance is unreachable from the workflow environment.
  • Dates off by hours — the Timezone setting does not match the SeaTable server’s timezone.

Frequently asked questions

Is the token per account or per base?

Per base. A workflow that touches two bases needs a credential for each, which also keeps access neatly scoped.

Why does the timezone matter?

Date values are interpreted against the SeaTable server's timezone. A mismatch shifts timestamps by hours without any error being raised.

What do I set for a self-hosted instance?

Environment to `selfHosted` and Domain to the instance's base URL. Cloud instances need neither changed.

Nodes that use SeaTable API

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

Last updated . Spotted something wrong? Tell us.