[setup] Register the Jaah Airtable OAuth app

**User-only setup task.** Only a person can do the registration steps below (it needs a human sign-in at the vendor). Runner: do NOT attempt the vendor-side steps yourself and do not open a PR. Ask the operator once through AskUserQuestion (header `Human act`) to do the steps; when they answer that it is done, run the **Runner validation** section on dev and settle with `no_pr` / `no_code_needed`, citing the observed Connect + Test result (never a secret value). If validation fails, say exactly which step looks wrong and ask once more. A person must do this: registering an app at Airtable needs a human sign-in at Airtable. It lets members connect Airtable to Jaah with one **Connect Airtable** button, without registering an app of their own. ## Steps 1. Sign in to Airtable with the account that should own Jaah's app (a shared company account, never a personal one), and open the developer console: https://airtable.com/create/oauth 2. Create a new OAuth app. Name it **Jaah**. 3. Select Register new OAuth integration, enter the name Jaah and the first redirect URI below, then select Register integration. 4. On the integration's page, under Scopes, tick user.email:read, schema.bases:read, data.records:read, data.records:write and data.recordComments:read, and nothing else. 5. Under Client secret select Generate client secret: Jaah is a server-side app and sends the secret with HTTP Basic auth. 6. Fill in the listing details: Tagline "AI agents that work your tasks", Homepage URL, Privacy policy URL and Terms of service URL set to the Jaah website, its privacy policy and its terms of service, Support email set to the Jaah support address, and upload the Jaah logo. 7. Select Save changes. 8. Add both redirect URIs exactly as written: `https://app.dev.jaah.ai/api/credentials/connect/callback` (dev) and `https://app.jaah.ai/api/credentials/connect/callback` (prod). If Airtable allows only one redirect URI per app, create a second app named **Jaah** for dev and do the paste step below once per environment. 9. Request exactly these scopes: `user.email:read`, `schema.bases:read`, `data.records:read`, `data.records:write`, `data.recordComments:read`. Why each one is needed is in the table below. 10. Copy the app's client ID and client secret. Keep them in your password manager only until the next step is done. 11. In the Jaah console of each environment (dev first, then prod), open **Secrets**, select **New**, and create an **OAuth app** (`oauth_app`) secret on the operator plane named `jaah-airtable-app`, with provider `airtable`, the client ID and the client secret. 12. Open **Settings > Integrations > OAuth apps > Airtable** and pick that secret in the knob `oauth_app.airtable`. 13. Never paste the client ID or secret into this task, a comment, a chat or an email. Reply here only with what you did. ## Scopes and why | Scope | Why Jaah asks for it | |---|---| | `user.email:read` | See your email address, so the connection shows whose it is | | `schema.bases:read` | Read base, table and field names, so agents know where data lives | | `data.records:read` | Read records, so agents can look things up | | `data.records:write` | Create and update records when a task asks for it | | `data.recordComments:read` | Read record comments for context | ## Redirect URIs - dev: `https://app.dev.jaah.ai/api/credentials/connect/callback` - prod: `https://app.jaah.ai/api/credentials/connect/callback` ## Review or verification Not required: an Airtable OAuth integration works for every Airtable user once it has a privacy policy, terms and support email. Airtable allows several redirect URLs on one integration, so add both. ## Runner validation A runner checks the setup once you mark this task answered: on dev, **Connect Airtable** with the Jaah app ends on **Connected** and **Test** passes. It reads only the result, never the secret. ## Out of scope No code change. Do not edit the vendor spec, the catalog engine or any other credential. Never paste the client ID or secret into this task, a comment, a log or a report. ## Done means - The operator confirmed the steps are done. - On dev, the Airtable Connect screen no longer says "Jaah app not configured", the consent round trip ends on **Connected**, and **Test** passes — cited from what you observed.