n8n OAuth Integration Doesn’t Display Airtable Schema Permissions

The behavior you’re seeing is expected. When you set up an OAuth integration in Airtable with the necessary schema and record scopes (for example, including schema.bases:read along with data.records:read/write), the consent screen might not list those schema-specific scopes explicitly. Instead, it shows a more generic set of permissions.

Make sure you’ve done the following:

• In Airtable’s OAuth integration settings, you’ve selected the recommended scopes (e.g., data.records:read, data.records:write, schema.bases:read).
• You’ve copied the correct OAuth Redirect URL from your n8n credential and entered it in your Airtable integration.

Even if the consent screen doesn’t display every individual scope, once you complete the authorization, n8n will have the access needed to work with your bases’ schema. If after connecting you still encounter issues accessing the schema or performing actions that rely on the schema scope, double-check that the scopes in your OAuth integration are set up correctly.

If everything appears to be configured properly and issues persist, you might want to verify by testing an API request against the expected endpoints or reach out to the Airtable or n8n community for further assistance.