Documentation

Cloudflare D1

Connect TableR to Cloudflare D1, serverless SQLite, with an account ID, database ID, and API token, verifying the connection, and troubleshooting.

Cloudflare D1 is serverless SQLite reached through the Cloudflare API. Provide your account ID, the target database ID, and an API token with D1 access.

Overview

TableR reaches D1 through the Cloudflare API over HTTPS — there is no host or port to run. You authenticate with an API token and identify the database by account ID and database ID. D1 is SQLite under the hood, so the SQL you know applies.

  • Serverless — reached at api.cloudflare.com over HTTPS; no server to run.
  • Authentication — a Cloudflare API token with D1 access.
  • Identity — an account ID and a database ID select the target D1 database.

Before you start

  • Your Cloudflare account ID.
  • The database ID of the target D1 database.
  • An API token with D1 read/write access.

Connection fields

These fields match TableR's Cloudflare D1 connection form. The API token is stored in the operating system keyring, never in plain configuration files.

FieldRequiredDefaultNotes
HostYesapi.cloudflare.comHTTPS endpoint; the connection is always encrypted.
CredentialYesA Cloudflare API token with D1 access; stored in the OS keyring.
Account IDYesYour Cloudflare account.
Database IDYesThe target D1 database.

Connect with the form

  1. 1
    Choose Cloudflare D1

    Open the launcher and pick the Cloudflare D1 card.

  2. 2
    Add the API token

    Paste a token with D1 access; it is saved to the OS keyring.

  3. 3
    Enter the account ID

    Use your Cloudflare account ID.

  4. 4
    Enter the database ID

    Identify the target D1 database.

  5. 5
    Save and connect

    Save the profile so it reappears in the launcher, then connect.

Verify the connection

Once connected, open a SQL tab and run a quick check:

SELECT sqlite_version();
SELECT name FROM sqlite_master WHERE type = 'table';

The first statement returns the SQLite version D1 runs; the second lists tables.

Troubleshooting

SymptomLikely causeFix
Authentication error (403)Missing or wrong API token, or insufficient scope.Use a token with D1 access and re-check it; it is saved to the keyring.
Account not foundWrong account ID.Re-check the account ID in the Cloudflare dashboard.
Database not foundWrong database ID.Re-check the D1 database ID.
Rate limited (429)Too many API requests.Wait and retry; reduce the request frequency.

Next steps