Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | ## How do I set up custom OAuth credentials for Airtable? |
| 2 | |
| 3 | Use your own Airtable OAuth integration when you want users to see your app's name on the consent screen and control the credentials yourself. |
| 4 | |
| 5 | ### Create the Airtable OAuth integration |
| 6 | |
| 7 | 1. Sign in to Airtable and open the [Airtable developer hub](https://airtable.com/developers/web/api). |
| 8 | 2. In the left menu, under **Guide**, click **OAuth integrations**, then click **+ New OAuth Integration** in the top-right corner. |
| 9 | |
| 10 |  |
| 11 | 3. Enter a name and description. The website field is optional. Users see these details when they authorize your app. |
| 12 | 4. Under **Redirect URLs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config, with `https` and no trailing slash. |
| 13 | 5. Save the integration and copy the **Client ID** and **Client Secret**. |
| 14 | |
| 15 | ### Create the auth config in Composio |
| 16 | |
| 17 | 1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Airtable**. |
| 18 | 2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**. |
| 19 | |
| 20 |  |
| 21 | 3. Paste the **Client ID** and **Client Secret**, then click **Create Airtable Auth Config**. |
| 22 | 4. Click **Connect Account**. On the Airtable consent screen, select the bases or workspaces to grant and click **Approve**. Confirm the account shows as **Active**. |
| 23 | |
| 24 | See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow. |
| 25 | |
| 26 | ### Scopes |
| 27 | |
| 28 | The default auth config requests `data.records:read`, `data.records:write`, `data.recordComments:read`, `data.recordComments:write`, `schema.bases:read`, `schema.bases:write`, and `user.email:read`. Change the **Scopes** field on the auth config if your integration needs fewer. |
| 29 | |
| 30 | If the connection fails, check that the redirect URL in Airtable matches the auth config's `oauth_redirect_uri` exactly. |