Airtable
Read and update records in the Airtable bases you share with Jaah.
Connect it with: Sign in (OAuth), API key. Airtable's own documentation: https://airtable.com/developers/web/api/oauth-reference.
What agents can do
Connect Airtable so the agents working your tasks can reach it. With it connected, they can:
- Look up a record in a base, for example a customer, an order or a content item a task names.
- List a table's fields and views so a task can work with the right data.
- Create or update records when a task reports results back, if you granted write access.
- Read the comments on a record for context before acting on it.
Before you start
- An Airtable account with access to the bases agents should use.
- For an organization connection, an account that is a collaborator on every base agents need: the connection sees only the bases its account can see.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Airtable
This is the quickest way in: you sign in to Airtable and approve what Jaah asks for. You never copy a key.
- In Jaah, open Secrets and select New.
- Search for Airtable and select its card.
- Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
- Select Connect Airtable. Airtable's sign-in window opens.
- Sign in to Airtable if asked, check the access listed, and approve it.
- You land back in Jaah on the new secret, which reads Connected once its test passes.
If the button reads Jaah app not configured, this Jaah has no app registered at Airtable yet. Use an API key, or your own OAuth app, until it does.
Scopes Jaah requests
Jaah asks Airtable for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.
| Scope | Why Jaah asks for it | Required |
|---|---|---|
user.email:read | See your email address, so the connection shows whose it is | Yes |
schema.bases:read | Read base, table and field names, so agents know where data lives | Yes |
data.records:read | Read records, so agents can look things up | Yes |
data.records:write | Create and update records when a task asks for it | No — you may untick it |
data.recordComments:read | Read record comments for context | No — you may untick it |
Connect with an API key
Prefer this when you cannot sign in with Airtable — for example a service account, or a token your admin issued. On the Connect screen select Use an API key instead.
Find each value first:
- Personal access token: airtable.com/create/tokens > Create new token: add the scopes user.email:read, schema.bases:read, data.records:read (and data.records:write if agents should edit), add the bases agents may use under Access, then Create token and copy it - Airtable shows it once.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Airtable card.
- Name the secret and choose who can use it.
- Select Use an API key instead.
- Fill in Personal access token.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Register your own OAuth app at Airtable when your company requires apps it controls, or before this Jaah has an app registered there.
- Create an OAuth app in Airtable's developer console, https://airtable.com/create/oauth (Airtable's documentation).
- Set its redirect URI to
https://app.jaah.ai/api/credentials/connect/callback(on your own Jaah, its console address followed by/api/credentials/connect/callback). - Give it the scopes in Scopes Jaah requests.
- Copy its client ID and client secret.
- In Jaah, start a new Airtable secret, select Use your own OAuth app, paste both values and select Connect Airtable.
The client secret is stored with the connection, encrypted, like any other secret value.
Test the connection
Select Test on the secret. Jaah calls Airtable's API once (GET https://api.airtable.com/v0/meta/whoami) with the stored values, and shows who it answered as, or which value Airtable refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
A key connection hands the agent its fields: api_key.
Tell the agent in your task description which secret to use, for example “use the Airtable secret org/airtable”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Airtable once the test passes. Steps: Replace or delete a secret.
- Reconnect: when Airtable ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Airtable's side too, revoke Jaah in Airtable's settings, or revoke or delete the key at Airtable.
Limitations
- Agents reach only the bases you pick on Airtable's consent screen (or the token's Access list). Add a base later by reconnecting, or by editing the token at airtable.com/create/tokens.
- Agents cannot create bases, change field types, manage collaborators or change billing.
- Airtable limits each base to five API requests per second; a busy agent may be slowed down.
- Agents can do only what the connected Airtable account and its granted scopes allow.
Troubleshooting
Test says Airtable rejected the personal access token (401)
The token was deleted, regenerated or mistyped. Create a new token at airtable.com/create/tokens and select Replace on the secret.
Test passes but agents get 403 or NOT_FOUND for a base
The base is not in the token's Access list or was not picked at consent. Edit the token and add the base, or select Reconnect and tick it.
The test names an ID such as usr... instead of an email
The token lacks the user.email:read scope. It still works; add the scope if you want the email shown.
The secret shows Needs reconnect
Airtable ended the grant (the integration was revoked or the refresh token expired after 60 days unused). Select Reconnect and sign in again.
Still stuck? Select Test and read the result: it names the value Airtable refused and the status it answered.
FAQ
Can agents see every base in my account?
No. Only the bases you choose on the consent screen, or list in the token's Access section.
Do changes appear under my name?
Yes. Records an agent creates or edits show the connected account as the editor in the record history.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Airtable account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.