How to review membership applications with Airtable in Webflow Cloud without giving reviewers base access

A Next.js application mounted on a Webflow Cloud site can provide a restricted membership-review queue for Airtable applications, displaying only Pending records and allowing authenticated reviewers to approve or reject them with notes that are written back through Airtable’s API. The setup requires an Airtable base with correctly configured fields and a narrowly scoped personal access token, a Webflow site and Cloud project, plus a Next.js 15 project using npm and compatible Node.js tooling, with Next.js 15 specifically retained because Webflow Cloud middleware support differs from newer proxy conventions. The implementation uses server-side Airtable fetch calls, protected API Route Handlers, HTTP basic-auth middleware, and a server-rendered review page with client-side decision controls that account for the Webflow mount path. Deployment requires environment variables for Airtable credentials, authentication credentials, and the mounted base path, with sensitive values marked as secrets. Common failures include incorrect Airtable permissions or IDs, client requests missing the Webflow mount path, unsupported Edge runtime declarations, and mismatched Airtable Status options or date-field types. The guidance also notes production limitations, including the need for rate limiting, CSRF or same-origin protections, and checks that records remain Pending before an update, while suggesting future automation for applicant emails, form intake, and publishing approved members to Webflow CMS collections.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.