Connect Baserow or NocoDB

≈ 2 min Erweiterung Bearer Token

Before you start

• A Baserow or NocoDB account, cloud or self-hosted. Self-hosted addresses such as localhost work from the extension.
• The AWFlow browser extension. These steps run in the extension (the web app hands them to it).

Used by

• Baserow / NocoDB

Pick a method

Method	Use it when
Baserow database token Recommended	For Baserow (baserow.io or your own server).
NocoDB API token	For NocoDB (app.nocodb.com or your own server).

Set it up

Baserow database token (recommended)

1. Create the token. In Baserow, open Settings › Database tokens, click Create token, pick the workspace that holds the table and allow create, read, update and delete. Copy it.

2. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap Baserow / NocoDB in the list, then fill the rest.

   12345

   1. 1 Schritt 1: Pick Baserow / NocoDB Under Integration App / Service, pick Baserow / NocoDB. There is no Auth Type menu: Baserow / NocoDB uses a Bearer Token.
   2. 2 Schritt 2: Name it For example Baserow – leads. A Description is optional.
   3. 3 Schritt 3: Paste the token Paste the token into Bearer Token.
   4. 4 Schritt 4: Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Schritt 5: Click Create Credential Prüfen: the credential is listed on the Credentials page, ready to pick in nodes.

   Nummerierte Bereiche im Screenshot: 1. Integration App / Service: Baserow / NocoDB; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

3. In the node, choose Baserow, set Base URL (for example https://api.baserow.io) and the Table ID.

Check it's connected — 

Run List rows: the table’s rows come back.

NocoDB API token

1. Create the token. In NocoDB, open Account settings › Tokens, click Add new token and copy it.

2. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap Baserow / NocoDB in the list, then fill the rest.

   12345

   1. 1 Schritt 1: Pick Baserow / NocoDB Under Integration App / Service, pick Baserow / NocoDB. There is no Auth Type menu: Baserow / NocoDB uses a Bearer Token.
   2. 2 Schritt 2: Name it For example NocoDB – inventory. A Description is optional.
   3. 3 Schritt 3: Paste the token Paste the token into Bearer Token.
   4. 4 Schritt 4: Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Schritt 5: Click Create Credential Prüfen: the credential is listed on the Credentials page, ready to pick in nodes.

   Nummerierte Bereiche im Screenshot: 1. Integration App / Service: Baserow / NocoDB; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

3. In the node, choose NocoDB, set Base URL (for example https://app.nocodb.com) and the Table ID.

Check it's connected — 

Run List rows: the table’s rows come back.

Where your token lives

Where your token lives — 

The credential is stored where you choose when you create it:

• Local (this browser only): encrypted in this browser. The encryption key is kept on the same device, so turn on the local secret vault to lock it with a passphrase only you know.
• Cloud (synced to your account): sent over an encrypted connection and stored encrypted on AWFlow’s server, so it works on your other devices.

When a step runs, your browser sends it only to the Base URL you set in the node (for example api.baserow.io or app.nocodb.com). AWFlow’s servers never relay the call.

Privacy & your data →

Common issues

• “Baserow API Error: 401” or “NocoDB API Error: 401”. The token is wrong or doesn’t cover this table. Create one that does.
• “404 Not Found”. Check Base URL (no path after the address, right port) and Table ID.
• The run is blocked in the web app. Baserow / NocoDB runs through the browser extension. Install the extension and allow Baserow / NocoDB for this workflow when asked, or run the workflow from the extension. See Extension-only integrations in the web app.

Related

Baserow / NocoDB node

All connections

Create and manage credentials

Privacy & your data